Skip to content
Skills Library
Programming · Review & audit

dev-design

/dev-design

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.

Repository
ai-devkit ↗
Licence
Apache-2.0
Last repository change
25.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 25.10.2026, without references to retired models or APIs.

Licence

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

What it does and when to use it

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.

Original author description

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 it works

  1. Phase Contract
  2. Review Design
Original SKILL.md headings · 36 lines, 401 words
SKILL.md preview
---
name: dev-design
description: 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.
---

# 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

1. Run `npx ai-devkit@latest lint` before phase work.
2. If working on a named feature, run `npx ai-devkit@latest lint --feature <name>`.
3. Read existing requirements and design docs before changes.
4. Ask until every material architecture, scope, validation, rollout, contradiction, trade-off, or open question is answered, explicitly deferred, or accepted as a named assumption.
5. Ask one decision at a time, with why it matters, 2-3 viable options when useful, and a recommended answer.
6. Do not approve or transition past design while material open questions remain.
7. Use mermaid diagrams for architecture visuals where a diagram clarifies the design.
8. If parent `dev-lifecycle` established usable task tracing, emit design phase, progress, blocker/open-question, and next-step events per `task`.

## Review Design

Use for Phase 3.

1. 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.json` `paths.docs`, falling back to `docs/ai`.
2. Search memory for relevant architecture patterns or past decisions.
3. Cross-check against the latest matching requirements doc. Verify every goal, user story, and constraint has corresponding design coverage. Flag uncovered requirements.
4. Review completeness: architecture, components, technology choices, data models, API contracts, design trade-offs, and non-functional requirements.
5. Check usage-first design: APIs, CLI flows, UI flows, and docs should optimize for their caller/user, not implementation convenience.
6. Screen design red flags: shallow modules, pass-through layers, temporal decomposition, leaked transport/storage/framework types, scattered validation, synchronized flags, and repeated conditionals where a domain model would fit.
7. Resolve every gap, misalignment, open question, hidden assumption, or unresolved trade-off between requirements and design.
8. Brainstorm alternatives for key architecture decisions and trade-offs before accepting the first approach.
9. Prefer subtract-before-add sequencing: delete obsolete paths, consolidate redundant concepts, and narrow scope before adding new structure.
10. Update the design doc with clarified decisions and chosen options.
11. Store reusable architecture decisions in memory.
12. If task tracing is available, record design coverage progress, next step, or blockers per `task`.
13. 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.
Files in this package (2)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · codeaholicguy/ai-devkit90Apache-2.0
pi-ixel/awesome-agent-workflow100MIT
tejitpabari99/tejit-plugin100MIT
lflish/devflow100MIT
FOURTEEN1416/academic-agent-toolkit96CC-BY-4.0

Identical content appears in 1 other GitHub folders. We show one copy with the highest score.

Database snapshot: 13.11.2026 · package version 259280c90101 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 90dev-requirements
    AI DevKit · Requirements phase guidance for starting features and reviewing requirements. Use when the user wants to capture a new requirement, clarify product scope, initialize feature docs, review requirements, or run dev-lifecycle phases 1-2.
  • 90dev-implementation
    AI DevKit · Implementation phase guidance for executing feature plans and checking implementation against design. Use when the user wants to implement planned tasks, update implementation docs, verify code matches design, or run dev-lifecycle phases 5 and 7.
  • 90write-design-docs
    Write, revise, or review software design documents using Malte Ubl's "Design Docs at Google" guidance. Use when Codex needs to draft a design doc, technical design, RFC, engineering review doc, architecture proposal, mini design doc, or design-doc review focused on context,…
  • 90dev-reviewing-design
    G2 gate review. Use for its verdict: judges architecture, impact, ADRs and threat model against the checklist and writes the gate log.
  • 100architecture-designer
    System architecture design/review:diagrams, ADRs, tech trade-offs, component interactions, scalability, microservices, infrastructure patterns. Use for system design, architecture review, ADR authoring. Not for code-level design patterns or database-only tasks.
  • 92weigh
    Evaluate architecture decisions, document trade-offs, select patterns for context. Use when making technology choices, evaluating architectural patterns, writing Architecture Decision Records (ADRs), assessing technical debt, or comparing design alternatives. Findings stay…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.