design

Authors codebase-grounded feature design documents through a four-phase interactive workflow.

1.4k|335|Updated Jun 10, 2014
One-click install
npx skills add https://github.com/openwpm/OpenWPM --skill design-openwpm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/openwpm/OpenWPM/tree/main/.claude/skills/design
Command: npx skills add https://github.com/openwpm/OpenWPM --skill design-openwpm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Turning a rough feature idea into a validated design document requires exploring the codebase, resolving ambiguities, and structuring requirements—work that is often skipped or done inconsistently. This Skill drives that process end to end and produces a design doc ready for pipeline kickoff. ## Core Features & Use Cases - Codebase-Grounded Exploration: Gathers context from issues, architecture files, and code search before asking clarifying questions that reference concrete files and functions. - Structured Design Documents: Writes .design/<slug>.md with requirements, mechanically testable acceptance criteria, architecture notes, and tracked open questions. - Interactive Iteration & Validation: Resolves open questions conversationally, validates document quality, stores the doc as a knowledge page, and initializes a pipeline state file for crosslink kickoff. - Use Case: A developer says "design batch retry logic for sync" and receives a validated design doc grounded in the actual sync module, with unresolved decisions flagged as open questions. ## Quick Start Ask the assistant to design a feature, for example: design a document for adding batch retry logic to the sync module.

Frequently Asked Questions about design

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

FAQPage Schema
How do I write a feature design document from a rough idea?

Invoke the design skill with a quoted feature description. It explores the codebase, asks clarifying questions grounded in real files, then drafts a structured document with requirements, acceptance criteria, and architecture notes in .design/<slug>.md.

How do I resume iterating on an existing design doc?

Pass --continue with the document slug, for example /design --continue add-batch-retry-logic. The skill reads the existing draft, detects unresolved open question blocks, and strengthens the document based on your answers.

Can the design skill pull context from GitHub issues?

Yes, pass --gh-issue <number> to read a GitHub issue via gh issue view, or --issue <id> to read a crosslink issue. The issue content informs the exploration and clarifying questions.

What happens to unresolved open questions in a design doc?

Unresolved ambiguities remain as <!-- OPEN --> blocks in the document, which is still valid but flagged during validation. You can resolve them interactively in a later iteration or edit the file directly.

Does the design skill modify source code or start implementation?

No, it only writes files under .design/ and never modifies source code. It suggests next steps like crosslink kickoff but does not run planning or implementation commands automatically.