techpacks

Read techpack.yaml manifests, resolve paths, and route commands between systems.

39|3|Updated Nov 21, 2025

Search Tags:#routing #manifest #workflow-orchestration #skill-loading #path-resolution #agent-spawn #techpack

Ready to run

npx skills add https://github.com/LiorCohen/sdd --skill techpacks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: techpacks
Source: https://github.com/LiorCohen/sdd/tree/main/plugin/core/skills/techpacks
Command: npx skills add https://github.com/LiorCohen/sdd --skill techpacks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes and streamlines tech-pack orchestration by providing a single entry point that reads manifests, resolves paths, and routes commands between core systems and tech-pack skills.

Core Features & Use Cases

Reads and validates techpack.yaml manifests and component configurations.
Resolves internal and external paths, loads skills and agents, and routes commands to the appropriate routers.
Supports loading and composing sub-skills and agents to enable end-to-end workflows across plan-generation, implementation, and verification phases.

Quick Start

Run a command to load a tech-pack, resolve a path, and route a command through the router to execute a workflow.

Frequently Asked Questions about techpacks

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How does tech-pack orchestration work for routing commands between core systems and skills?▼

Tech-pack orchestration works by reading techpack.yaml manifests, resolving internal and external paths, and routing commands to appropriate routers to coordinate skill loading and agent spawning across core systems.

How do I load skills and spawn agents during the plan-generation phase?▼

To load skills and spawn agents during plan-generation, you run a command through the orchestration gateway, which reads the manifest, resolves paths, and structures command routing for the workflow.

What is the best way to resolve internal and external paths when loading a tech-pack?▼

The best way to resolve internal and external paths is by using an orchestration gateway that reads and validates techpack.yaml manifests to coordinate component routing and path resolution across software projects.

Do I need a techpack.yaml manifest to use workflow orchestration for my software project?▼

Yes, you need a techpack.yaml manifest because the orchestration gateway reads and validates these component configurations to load sub-skills and route commands across implementation and verification phases.

Can I compose sub-skills and agents to support end-to-end implementation workflows?▼

Yes, you can compose sub-skills and agents because the orchestration gateway supports loading and composing these components to enable end-to-end workflows across plan-generation, implementation, and verification phases.

Why does command routing fail if paths are not resolved correctly in the orchestration workflow?▼

Command routing fails because the orchestration gateway relies on accurate path resolution from the manifest to successfully route commands between core systems and tech-pack skills during execution.