Stats
Actions
Tags
From ac-workflow
Orchestrates spec-driven development by triggering stage agents (CREATE, PLAN, IMPLEMENT, REVIEW, TEST). Manages spec files, AI-section edits, per-stage git commits. Activates on 'spec' keywords or /spec.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ac-workflow:specThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
/spec STAGE SPEC: STRICTLY FOLLOW ${CLAUDE_PLUGIN_ROOT}/agents/spec/{STAGE}.md using STAGE AND SPEC as the variables
/spec STAGE SPEC: STRICTLY FOLLOW ${CLAUDE_PLUGIN_ROOT}/agents/spec/{STAGE}.md using STAGE AND SPEC as the variables
STAGE=$ARGUMENTS SPEC=$ARGUMENTS / LAST USED SPEC
spec(<NNN>): <STAGE> - <title>When working with external specs storage, read:
${CLAUDE_PLUGIN_ROOT}/scripts/spec-resolver.sh${CLAUDE_PLUGIN_ROOT}/scripts/external-specs.sh${CLAUDE_PLUGIN_ROOT}/scripts/lib/config-loader.shnpx claudepluginhub waterplanai/agentic-config --plugin ac-workflowTransforms ideas into structured specifications (requirements, design, tasks) before implementation. Use when building features, fixing bugs, refactoring, or designing systems.
Guides spec-driven development through phases: research, requirements, design, tasks, autonomous task-by-task implementation. Decomposes large epics into ordered specs with progress tracking.
Writes structured specifications before coding. Use when requirements are ambiguous, starting a new project/feature, or changes touch multiple files.