tech-spec

To generate a technical spec without writing code, provide the feature requirements and project context. The skill analyzes the codebase and outputs subphase documents with file paths, schemas, and test plans, ensuring no application code is generated during planning.

A subphase document is a detailed technical execution blueprint generated from project context. It decomposes requirements into specific file paths, data schemas, and test plans, guiding implementation and testing without altering production code.

Yes, you can use this to plan database migrations and major refactors. It automates creation of execution specs by thoroughly analyzing a codebase and producing subphase documents with exact file paths and test plans for new features or migrations.

The best way to decompose requirements into schemas and test plans is using deep codebase analysis to map current state and dependencies. This generates subphase documents containing exact file paths, data schemas, and test plans to guide implementation.

Yes, the technical spec generation process references project-specific configuration for conventions and tooling. It performs exhaustive codebase discovery to ensure the output subphase documents align with existing project standards and requirements.

Technical spec output avoids code generation to satisfy planning requirements and prevent unintended production code changes. It focuses on producing detailed execution blueprints with file paths, data schemas, and test plans rather than writing application code.