get-shit-done

Spec-driven development enforces strict requirements and plans before any code execution begins. It manages project lifecycles through structured slash commands, ensuring focused execution and persistent state across milestones and phases.

You orchestrate milestones and phases by initiating the project with a structured slash command, then sequentially planning and executing individual phases to maintain a persistent project state from ideation to completion.

Meta-prompting for workflow automation is a technique that structures project execution through engineered context and spec-driven commands. It guides agent orchestration by enforcing requirements before development across complex project phases.

Yes, spec-driven development workflows support debugging, codebase mapping, and research tasks. These features are integrated directly into the structured phase execution and verification lifecycle to maintain context integrity.

No external dependencies are required. The workflow relies entirely on internal scripts, references, and templates to engineer context, orchestrate agents, and manage project state without integrating outside libraries.

You should avoid breaking work into atomic plans for simple, single-step tasks that do not suffer from context rot. The overhead of milestone planning and spec-driven constraints provides no benefit for trivial, isolated code modifications.