tech-spec-planning

To generate a technical specification, the skill researches your existing codebase, clarifies requirements, and defines an implementation plan. It integrates your user-spec requirements to outline architecture, actionable tasks, and validation strategies.

Writing a tech spec that ensures technical feasibility involves defining the architecture and outlining implementation tasks, followed by a multi-validator review process. This ensures the final document adheres to project standards before development begins.

Yes, you can use this skill to create an implementation plan for an authentication module. It will research your existing code, identify necessary changes, define the architecture, outline implementation tasks, and prepare the specification for review.

To structure implementation tasks in a technical specification document, the skill breaks down the feature into actionable items with assigned skills and reviewers. This structured breakdown is integrated into the generated tech-spec.md file.

Yes, technical specification generation requires a user spec file as input. The skill creates the tech-spec.md document based on your user-spec.md and existing project knowledge to ensure all technical aspects are clearly defined.

A limitation of automated tech spec generation is that it requires user approval during its multiple validation steps before finalization. You must actively participate in clarifying requirements to ensure the implementation plan meets project standards.