apdevflow

Transform JIRA epics into technical feature breakdowns organized by system components. Analyzes epic scope and creates numbered features with technical components, dependencies, and acceptance criteria. Outputs feed into feature-story-creator skill. Use when decomposing epics into deliverable features.

Transform features into user stories ready for dev-spec. Analyzes feature technical components and creates numbered stories with acceptance criteria, dependencies, and technical notes. Outputs feed into dev-spec skill. Use when decomposing features into implementable stories.

Deep analysis debugging mode for complex issues. Activates methodical investigation protocol with evidence gathering, hypothesis testing, and rigorous verification. Use when standard troubleshooting fails or when issues require systematic root cause analysis.

Execute specifications from configurable directory (defaults to ./.dev-docs/features/) in fresh sub-agent contexts. Two-phase workflow - Phase 1 implements and provides testing guidance, Phase 2 archives after user confirms testing complete. Supports single, parallel, and sequential execution.

Orchestrates systematic development workflow for any software development task - from simple bug fixes to complex multi-file features. Separates specification from implementation, provides testing guidance, and manages completion workflow. Use when user requests to implement, build, develop, or fix any code.

Expert prompt engineer that creates optimized, XML-structured specifications for all software development tasks. Adapts specification depth based on task complexity - lightweight for simple bugs, comprehensive for complex features. Includes testing step generation guidance. Saves specifications to configurable directory (defaults to ./.dev-docs/features/).

Generates commits with clear commit messages from git diffs. Use when creating commits and writing commit messages.