draft-design

Transform requirements into a numbered DESIGN.md document for graph generation.

5|1|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/tonitangpotato/rustclaw --skill draft-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: draft-design
Source: https://github.com/tonitangpotato/rustclaw/tree/main/skills/draft-design
Command: npx skills add https://github.com/tonitangpotato/rustclaw --skill draft-design

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts scattered requirements into formal, numbered design documents that support deterministic GID extraction and engineering planning.

Core Features & Use Cases

  • Generates a complete DESIGN.md with numbered sections aligned to requirements.
  • Supports incremental writing: skeleton first, then fill each section through iterative edits.
  • Useful for Phase 3 of the GID pipeline and for refining designs before graph assembly.

Quick Start

Generate a DESIGN.md skeleton from the loaded requirements and iteratively fill each section.

Frequently Asked Questions about draft-design

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

FAQPage Schema
How do I turn scattered requirements into a structured design document?

To convert requirements into a structured design document, this Skill generates a formal, numbered DESIGN.md that maps to your project goals and enforces explicit interfaces. It provides a complete skeleton for incremental editing.

Can I generate a design doc incrementally instead of writing it all at once?

Yes, you can generate a design doc incrementally by first creating a DESIGN.md skeleton from loaded requirements, then iteratively filling each numbered section through targeted edits to refine the architecture.

What is the best way to prepare an engineering design doc for graph generation?

The best way to prepare an engineering design doc for graph generation is to enforce explicit interfaces, section numbering, and diagrams, supporting deterministic GID extraction for subsequent graph assembly.

Does this design doc generator support verification against existing code?

Yes, the design doc generator supports verification against style rules and existing code when available, ensuring the formal architecture documentation aligns with your current engineering constraints.

When do I need to use a numbered design document for software architecture?

You need a numbered design document for software architecture when working on multi-feature projects or single-feature efforts that require deterministic GID extraction and structured engineering planning.

Can I use this for both single-feature efforts and multi-feature projects?

Yes, you can use this for both single-feature efforts and multi-feature projects, as it transforms requirements into formal, numbered design documents that map to goals and support incremental section extension.