draft-design-revision

Draft and refine design revisions with clarifying-question triage and adversarial review.

26|3|Updated Oct 9, 2025
One-click install
npx skills add https://github.com/davidlee/spec-driver --skill draft-design-revision
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-design-revision
Source: https://github.com/davidlee/spec-driver/tree/main/.spec-driver/skills/draft-design-revision
Command: npx skills add https://github.com/davidlee/spec-driver --skill draft-design-revision

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafting a design revision (DR) for a delta is hard because it requires converting fuzzy intent and constraints into a validated, section-by-section target design that stays aligned with the delta scope and is ready for downstream planning.

Core Features & Use Cases

  • Guided DR shaping for implementability: Translates delta intent into a DR with explicit code-impact and verification alignment.
  • Clarifying-question triage loop: Uses a one-question-at-a-time flow to resolve purpose, constraints, and success criteria before writing the design.
  • Adversarial review and reconciliation: Performs hostile self-review to expose ambiguity, missing governance constraints, and weak verification, then integrates feedback back into the DE/DR before planning.
  • Planning transition: Hands off to the plan-phases skill to produce implementation IP/phase artifacts once the DR is approved.

Quick Start

Use the draft-design-revision skill to create a DR for delta DE-XXX by providing the DE-XXX file, any existing DR-XXX artifact, and the relevant specs/requirements/backlog.

Frequently Asked Questions about draft-design-revision

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I translate delta intent into an implementable design revision?

To translate delta intent into an implementable design revision, you draft and refine a DR section-by-section, validating fuzzy constraints against delta scope to produce verifiable design sections with explicit code-impact. This ensures the target design remains aligned with the delta scope.

What is the best way to validate a design revision before implementation planning?

The best way to validate a design revision is through an adversarial review that performs a hostile self-review to expose ambiguity, missing governance constraints, and weak verification, then integrates that feedback back into the design before planning.

How does clarifying-question triage work for spec-driven development?

Clarifying-question triage in spec-driven development uses a one-question-at-a-time flow to resolve purpose, constraints, and success criteria before writing the design, ensuring the design revision is fully validated against the delta scope.

Can I transition an approved design revision directly into implementation phases?

Yes, once a design revision is approved, you can transition it into implementation planning by handing off to the plan-phases skill, which produces the downstream implementation IP and phase artifacts needed for execution.

What do I need to provide to draft a design revision for a delta?

To draft a design revision for a delta, you need to provide the delta file, any existing design revision artifact, and relevant specs, requirements, or backlog history to ensure proper doctrine constraints and DE/DR alignment.

Why does my design revision lose alignment with the delta scope?

A design revision loses alignment with the delta scope when it fails to maintain DE/DR alignment or skips reading relevant specs and doctrine constraints, which this skill resolves by enforcing section-by-section validation and explicit verification evidence.