Dev Design
Developmentdev-designDev Design is an Agent Skill for development published in the codeaholicguy/ai-devkit repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
AI DevKit · Design phase guidance for reviewing feature design against requirements. Use when the user wants to validate architecture, review design docs, resolve design trade-offs, or run dev-lifecycle phase 3.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/codeaholicguy/ai-devkit/blob/HEAD/skills/dev-design/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/dev-design, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Dev Design
Run the design review phase for configured AI docs features. Before changing docs or code, propose the concrete plan for this phase and wait for user approval unless the user already approved the exact phase plan.
Phase Contract
- Run
npx ai-devkit@latest lintbefore phase work. - If working on a named feature, run
npx ai-devkit@latest lint --feature <name>. - Read existing requirements and design docs before changes.
- Ask until every material architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly deferred, or accepted as a named assumption.
- Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer.
- Do not approve or transition past design while material open questions remain.
- Use mermaid diagrams for architecture visuals where a diagram clarifies the design.
- If parent
dev-lifecycleestablished usable task tracing, emit design phase, progress, blocker/open-question, and next-step events pertask.
Review Design
Use for Phase 3.
- Run
npx ai-devkit@latest lint --feature <name>and review the design doc path it validates. If manual path resolution is unavoidable, first resolve.ai-devkit.jsonpaths.docs, falling back todocs/ai. - Search memory for relevant architecture patterns or past decisions.
- Cross-check against the latest matching requirements doc. Verify every goal, user story, and constraint has corresponding design coverage. Flag uncovered requirements.
- Review completeness: architecture, components, technology choices, data models, API contracts, design trade-offs, and non-functional requirements.
- Resolve every gap, misalignment, open question, hidden assumption, or unresolved trade-off between requirements and design.
- Brainstorm alternatives for key architecture decisions and trade-offs before accepting the first approach.
- Update the design doc with clarified decisions and chosen options.
- Store reusable architecture decisions in memory.
- If task tracing is available, record design coverage progress, next step, or blockers per
task. - Summarize requirements coverage, completeness assessment, updates made, and remaining gaps.
Next: dev-implementation. If requirements gaps are found, return to dev-requirements. If design is fundamentally wrong, revise design and re-review.