.build/claude/skills/skill-chain-prompts/SKILL.md
Orchestrate multi-skill workflows with prompt-based skill chaining. Define sequential or parallel skill invocations using YAML chain definitions, track progress through chains, and use pre-built chains for development, documentation, and career workflows. Use when coordinating multiple skills for complex tasks.
npx skillsauth add organvm-iv-taxis/a-i--skills skill-chain-promptsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Orchestrate complex workflows by chaining multiple skills together. Define sequences, track progress, and use pre-built chains for common development patterns.
A chain is a sequence of skills that work together to accomplish a larger goal. Each step invokes a skill, passes context forward, and tracks completion. Chains work through Claude's sequential processing—no external engine required.
chain:
name: "my-workflow"
description: "What this chain accomplishes"
steps:
- id: first
skill: skill-name
description: "What this step does"
outputs: [artifact1, artifact2]
- id: second
skill: another-skill
depends_on: [first]
checkpoint: true # Pause for review
- id: third
skill: final-skill
depends_on: [second]
optional: true # Can be skipped
| Command | Purpose |
|---------|---------|
| /skill-chain-prompts run <chain> | Execute a named chain |
| /skill-chain-prompts list | Show available chains |
| /skill-chain-prompts status | Display current progress |
| /skill-chain-prompts resume | Continue from checkpoint |
| /skill-chain-prompts skip | Skip current optional step |
api-development — Full API from design to deployment
api-design-patterns → tdd-workflow → backend-implementation-patterns → verification-loop → deployment-cicd
fullstack-feature — Complete feature implementation
product-requirements-designer → api-design-patterns → backend-implementation-patterns → frontend-design-systems → testing-patterns → verification-loop
mcp-development — MCP server creation
mcp-builder → testing-patterns → verification-loop → mcp-server-orchestrator
career-preparation — Job search readiness
cv-resume-builder → portfolio-presentation → interview-preparation → networking-outreach
documentation — Project documentation
doc-coauthoring → github-repository-standards → github-profile-architect
User: /skill-chain-prompts run api-development
Claude: Starting chain: api-development
"Full API development from design to deployment"
Step 1/5: design (api-design-patterns)
Invoking /api-design-patterns...
User: /skill-chain-prompts status
Claude: ## Chain Progress: api-development
| Step | Skill | Status | Notes |
|------|-------|--------|-------|
| design | api-design-patterns | ● Done | OpenAPI spec created |
| test-first | tdd-workflow | ◐ Active | Writing endpoint tests |
| implement | backend-implementation-patterns | ○ Pending | |
| verify | verification-loop | ○ Pending | |
| deploy | deployment-cicd | ⊖ Optional | |
**Progress**: 2/5 steps (40%)
**Current**: test-first
User: I need a chain for building a CLI tool
Claude: Creating custom chain...
chain:
name: "cli-tool"
description: "Build a CLI application"
steps:
- id: design
skill: api-design-patterns
description: "Design CLI interface and commands"
- id: implement
skill: backend-implementation-patterns
depends_on: [design]
- id: test
skill: testing-patterns
depends_on: [implement]
- id: docs
skill: doc-coauthoring
depends_on: [implement]
optional: true
Ready to execute?
Progress is tracked in the conversation using markdown tables:
## Chain Progress: fullstack-feature
| Step | Skill | Status | Notes |
|------|-------|--------|-------|
| requirements | product-requirements-designer | ● Done | PRD complete |
| api | api-design-patterns | ● Done | 12 endpoints |
| backend | backend-implementation-patterns | ◐ Active | 8/12 endpoints |
| frontend | frontend-design-systems | ○ Pending | |
| testing | testing-patterns | ○ Pending | |
| verify | verification-loop | ○ Pending | |
**Progress**: 2.5/6 steps (42%)
**Checkpoint**: After verify
| Icon | Meaning | |------|---------| | ○ | Pending | | ◐ | In Progress | | ● | Complete | | ⊖ | Optional/Skipped | | ✕ | Failed |
Checkpoints pause the chain for review:
- id: verify
skill: verification-loop
depends_on: [implement]
checkpoint: true # Chain pauses here
At a checkpoint:
/skill-chain-prompts resume continuesreferences/chain-format.md — Complete YAML specificationreferences/execution-model.md — How chains are processedreferences/state-tracking.md — Progress visualization formatsreferences/built-in-chains.md — All pre-built chains documentedPre-built chain files in assets/chains/:
api-development.yamlfullstack-feature.yamlcareer-preparation.yamlmcp-development.yamlcustom-chain.yaml — Blank templatedevelopment
Dry-run audit + targeted cleanup for shell command history. Currently wraps atuin (stats today, prune, dedup with dated preview artifacts); extensible to zsh/bash/mcfly backends. Always previews before applying — apply commands are echoed for the human to run, never auto-executed. Triggers on "/shell-history-hygiene", "audit atuin", "audit shell history", "clean shell history", "atuin prune", "atuin dedup", "shell history hygiene", "history cleanup". Replaces ad-hoc one-liners (e.g. `... | tee cmd > file.txt` which wrote two files, swallowed dedup output, and left a junk `cmd` file).
tools
Guided Cowork setup — install role-matched plugins, connect your tools, try a skill.
development
Manage AI agent session lifecycles with structured phases (FRAME, SHAPE, BUILD, PROVE), context preservation across sessions, handoff protocols, and session metadata tracking. Triggers on session management, agent lifecycle, or multi-session workflow requests.
tools
Parse a session transcript into a structured Session Governance Index — an annotated bibliography of every file modified and commit made, internal-energy accounting (tool uses, estimated tokens), shipped-vs-tasked atom tally, and classification of missing items as Gaps or Vacuums. Triggers on "visibility-schema-substrate-sweep", "session cascade audit", "session governance audit", or any request to summarize what a session actually produced versus what it was asked to produce.