generate-spec

To generate a detailed implementation spec, this Skill analyzes your existing codebase and external documentation to define problems, propose solutions, and outline phased implementation steps for new features. It structures the document with goals, non-goals, and critical clarifying questions.

A phased specification document includes a problem overview, proposed solution, specific goals, non-goals, and step-by-step implementation phases. It leverages codebase analysis and critical questioning to resolve ambiguities before coding begins.

You document complex bug fixing plans by generating a structured specification that outlines the problem, solution, and implementation steps. The Skill asks critical questions to clarify requirements and establish a robust plan before any coding begins.

Yes, you can generate specifications by relying primarily on existing codebase analysis to inform the plan. However, providing external documentation helps the Skill better define problems, establish goals, and propose more accurate solutions.

The best way to define goals and non-goals for an implementation plan is using a structured specification generator. This Skill analyzes your codebase and documentation to explicitly establish boundaries and objectives before development starts.

You need a specification document when proposing a significant new feature or tackling a complex bug fix. It ensures a robust plan by resolving ambiguities through critical questioning before the actual implementation phase begins.