home/dot_claude/exact_skills/design-doc/SKILL.md
Creates design documents using Prompt-Driven Development to refine ideas into structured proposals. Use when user mentions design doc, design document, RFC, technical proposal, architecture proposal, write a proposal, or PDD. Do not use for implementation plans, code reviews, bug fixes, or task tracking.
npx skillsauth add guicaulada/dotfiles design-docInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create structured design documents using Prompt-Driven Development (PDD). Guides users through iterative refinement of rough ideas into comprehensive design documents with multiple proposals, trade-off analysis, and consensus tracking.
| Section | Purpose | |------------|-----------------------------------------| | Background | Sets context in 1-2 paragraphs | | Problem | Explains why action is needed now | | Goals | Defines success criteria and priorities | | Proposals | At least 2-3 options with trade-offs | | Do Nothing | Always included as Proposal 0 baseline | | Consensus | Documents decision and participants |
The skill follows the Prompt-Driven Development methodology — iterative refinement through requirements clarification, research, and checkpoint reviews before generating the design document. The full process is embedded in the create workflow.
Trigger: "design doc", "design document", "RFC", "technical proposal", "architecture proposal", "write a proposal", "PDD"
Should NOT trigger: "implement the feature", "review this PR", "fix this bug", "create a task list", "write tests"
Read and follow create.md.
testing
Fetches GitHub issues, pull requests, reviews, notifications, and project board data for the user and optionally teammates, then analyzes their state and produces a prioritized work plan. Use when prioritizing work, triaging GitHub activity, planning what to work on next, assessing current workload, checking sprint status, or reviewing project board items. Supports teammate usernames and focus areas via arguments. Do NOT use for creating, modifying, or closing issues, PRs, or other GitHub resources.
testing
Transforms text into exhaustive structured bullet-point summaries for studying and test preparation. Use when user mentions summarize, create a summary, bullet point this, give me the key points, study notes, help me study, prepare for exam, create study guide, or make flashcard content.
development
Reviews pull requests with detailed code analysis and feedback. Use when user mentions review pr, pr review, review pull request, check pr, analyze pr, code review, review prs, batch review. Not for dependency bump PRs (use /review-deps instead).
testing
Reviews dependency bump PRs with focus on compatibility and security issues. Use when user mentions review deps, review dependencies, dependency review, check deps, dependency prs, dep bumps, review deps prs, batch dep review.