Translate approved product specifications into feature tech-spec documents.
npx skills add https://github.com/csackrider/AI-DLC --skill design-csackrider
Please help me install this Agent Skill. Skill: design Source: https://github.com/csackrider/AI-DLC/tree/main/plugins/ai-dlc-skills/skills/design Command: npx skills add https://github.com/csackrider/AI-DLC --skill design-csackrider
Design phase execution requires converting an approved Product Spec into a concrete Tech Spec that can guide implementation. This skill provides a structured process to translate intent into scope, architecture, data models, and acceptance criteria, ensuring traceability and a formal gate before build.
Translate the approved product spec into the tech-spec in the feature folder and prepare the human gate before the build.
High-intent search queries and answers about installing and using this skill.
To translate a product spec into a tech spec, use this skill to convert approved intent into a concrete design-tech specification. It documents scope, architecture, data models, and acceptance criteria within the feature directory to guide implementation.
The best way to document architecture and data models is generating a detailed tech-spec.md file in the feature folder. This process codifies technical scope, API/UI contracts, and testing approach to ensure traceability before the build phase.
To enforce human approval gates before build, the skill prepares a formal review step cross-referencing related plans and ADRs. This ensures the tech-spec documentation satisfies gating requirements requiring human approval prior to implementation.
Yes, you can cross-reference ADRs and related plans within your design documentation. The skill enforces linking related ADRs, ADR templates, and spec-management guidance directly inside the generated tech-spec to maintain formal traceability.
Yes, this design workflow supports codifying acceptance criteria and testing approach. It translates an approved product specification into a detailed design-tech specification that explicitly documents these elements alongside architecture and data models.
You need a formal tech-spec for your feature directory when a feature's technical scope, architecture, and acceptance criteria must be codified and reviewed. This skill enforces a formal gate requiring human approval before proceeding to build.
NebulaMaoGenerate technical implementation plans from feature specifications.
miles990Converts design documents into structured AI-ready technical specifications with Given-When-Then acceptance criteria, API definitions, and tech-spec.md output.
pradeepmouliConvert feature specifications into structured plan.md technical designs.
taku-oTranslate product requirements into architecture-ready technical design specifications.
