// Use when the user says /docs or asks for end-to-end documentation workflows like API docs, project scaffolding, content pipelines, or release documentation - routes to the right pipeline and invokes pipeline-orchestrator to execute it
Use when the user asks about agent pipelines, how to use /code /docs /startup commands, how to create custom pipelines, or needs help troubleshooting agent workflows - explains the agent orchestrator system and guides pipeline creation
Use when the user wants to create a custom agent pipeline, add a new pipeline to an existing agent, or design a multi-stage workflow that chains skills together - guides through pipeline JSON creation with validation
Use when a super-agent (coding-agent, docs-agent, startup-agent) needs to execute a multi-stage pipeline defined in JSON - resolves template variables, manages sequential/parallel/chain stage execution, enforces quality gates, and passes data between stages via file outputs
Use when the user says /code or asks for end-to-end coding workflows like full-stack builds, quality audits, rapid prototypes, or debug chains - routes to the right pipeline and invokes pipeline-orchestrator to execute it
Use when the user says /startup or asks for end-to-end startup workflows like MVP builds, go-to-market launches, pitch decks, or product analytics - routes to the right pipeline and invokes pipeline-orchestrator to execute it
Create detailed technical plans and implementation roadmaps by analyzing project architecture and designing solutions that integrate seamlessly with existing patterns. Use when designing features, planning integrations, making architectural decisions. Triggers: 'plan', 'design', 'architecture', 'approach', 'how should I', 'best way', 'integrate', '계획', '설계', '아키텍처', '접근법', '어떻게 해야', '가장 좋은 방법', '통합', '마이그레이션', working with multi-module features, system boundaries, complex migrations.
| name | docs-agent |
| description | Use when the user says /docs or asks for end-to-end documentation workflows like API docs, project scaffolding, content pipelines, or release documentation - routes to the right pipeline and invokes pipeline-orchestrator to execute it |
I'm using the docs-agent skill to orchestrate a documentation pipeline.
| Command | Pipeline | What It Does |
|---|---|---|
/docs api | api-docs.json | API documenter → code documenter → examples → OpenAPI spec |
/docs project | project-docs.json | Scaffold CLAUDE.md → ARCHITECTURE.md → DEVLOG.md → DOMAIN.md |
/docs content | content-pipeline.json | Research → parallel content (Medium, LinkedIn, newsletter) → polish |
/docs release | release-docs.json | PR review → commit helper → changelog → release notes |
If the user specifies a pipeline (e.g. /docs api), load it directly.
If the user says just /docs or describes a task without specifying a pipeline, present the options:
Ask the user which pipeline fits their task:
Ask the user for:
references/pipelines/{pipeline}.jsonpipeline-orchestrator to execute the pipelineREQUIRED SUB-SKILL: agents/pipeline-orchestrator
After the orchestrator finishes, summarize:
/docs or "document this", "write docs", "create changelog"pipeline-orchestrator (always), plus skills defined in pipeline JSONscontent-creation, document-processing