rodrigobranas/aidev_axon_7/create-techspec

Create TechSpec

Core Workflow

Use this skill to turn an existing PRD into a concise, implementation-ready technical specification saved in the project task structure.

Read resources/create-techspec.md before starting. Treat that file as the canonical workflow for this skill.

Load resources/techspec-template.md only after PRD analysis, project exploration, research, and technical clarification, when drafting the tech spec. Treat that file as the required TechSpec template standard.

Execution Rules

• Confirm and read the PRD at tasks/prd-[feature-name]/prd.md.
• Explore the project before asking technical clarifying questions.
• Use Context7 MCP for technical documentation questions when relevant.
• Use web search for business rules and general information before clarifying when the workflow requires it.
• Ask focused technical clarifying questions before drafting the tech spec.
• Generate the tech spec from the exact template in resources/techspec-template.md.
• Focus on technical guidance and architecture; do not implement code.
• Avoid repeating PRD functional requirements except where needed to anchor technical choices.
• Save the final tech spec to tasks/prd-[feature-name]/techspec.md.
• Report the final file path and confirmation.

Expected Inputs

Typical input is a PRD path, feature name, or request such as:

• "Use $create-techspec for tasks/prd-team-invitations/prd.md."
• "Create a tech spec for the checkout-flow PRD."
• "Turn this PRD into an implementation-ready technical specification."

If the feature directory is unclear, inspect tasks/prd-* directories and ask for clarification only when multiple plausible PRDs exist.