plan-implementation

To generate an implementation plan from a technical spec, the Skill auto-detects your project structure and translates specs into file-by-file plans, defining interfaces, dependency graphs, and test strategies aligned to existing patterns.

Coordinating team implementation work requires establishing a correct build order and checkpoints. This Skill orchestrates that path by ensuring every code change traces back to a spec requirement and managing progress artifacts for team alignment.

To resume implementation work after interruptions, you need managed checkpoints and progress artifacts. This Skill tracks these milestones and enforces Skeptic sign-off, allowing you to safely resume work exactly where the process was paused.

Yes, a defined spec in docs/specs is required. This workflow specifically applies to software projects with existing technical specs, using them to identify required artifacts like interfaces, dependencies, and tests for the plan.

Defining interfaces with complete type signatures is handled by extracting artifact requirements directly from the technical spec. The Skill ensures all generated interface definitions are fully typed and correctly ordered within the dependency graph.

A spec-driven planning workflow ensures every change traces back to a spec requirement, preventing scope creep. Unlike ad-hoc coding, it establishes a correct build order and defines a comprehensive testing strategy before development begins.