dev

You orchestrate end-to-end software development workflows by invoking the dev skill to coordinate planning, design, task decomposition, and build execution with deterministic handoffs. It manages the full pipeline through Plan, Design, Tasks, and Build stages.

The best way to manage multi-phase projects with deterministic handoffs is using an orchestration skill that enforces strict inputs and outputs across phases. It generates artifacts like PRDs, architecture docs, and ERDs to drive governance and traceability.

Yes, you can automate task decomposition and traceability by coordinating a suite of agents including planner-phase, planner-task, and dev-executor. These agents drive QA and track progress using a robust data model.

You generate and track development artifacts through artifact-driven governance across workflow stages. The system produces brainstorms, PRDs, architecture docs, ERDs, and worktree states, passing them as deterministic handoffs between each phase.

No, this development workflow orchestration requires no external dependencies or components to function. It operates entirely self-contained inside Claude Code to coordinate agents and manage artifact-driven governance.

Agent orchestration improves software development planning by coordinating primary and elevated agents like validators and reinforcers to drive QA. This approach enforces strict inputs and outputs, ensuring progress is tracked through a robust data model rather than manual oversight.