shouenlee/design_doc
plugins/design-doc/skills/design_doc/SKILL.md
Generates RFCs and Architecture Decision Records (ADRs) from feature descriptions — reads existing docs to maintain numbering and style. Use when asked to "write rfc", "create adr", "design doc", "architecture decision", "technical design", "write proposal", "document decision", or "design document".
testing
Updated Apr 14, 2026
$ install --global
skillsauthnpx skillsauth add shouenlee/ghcp-dev-plugin design_docInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 14, 2026, 2:27 AM60.1s1 file scanned
SKILL.md
- name:
- design_doc
- description:
- Generates RFCs and Architecture Decision Records (ADRs) from feature descriptions — reads existing docs to maintain numbering and style. Use when asked to "write rfc", "create adr", "design doc", "architecture decision", "technical design", "write proposal", "document decision", or "design document".
Design Document Generator
Generate RFCs and Architecture Decision Records (ADRs) that follow your project's existing numbering, format, and style conventions.
When to Use
- You need to write an RFC for a new feature proposal
- You need to record an architecture decision as an ADR
- You want to create a technical design document with consistent formatting
- You want to document a decision or proposal using your project's existing conventions
Prerequisites
None. The skill will create the docs directory if one does not already exist.
Workflow
-
Determine document type (RFC or ADR) from the user request:
- RFC: larger feature proposals with context, alternatives, and an implementation plan
- ADR: focused architecture decisions with status, context, decision, and consequences
-
Scan for existing docs to discover where documents live:
find . -type d -name "rfcs" -o -name "adrs" -o -name "decisions" -o -name "architecture" | head -20- Look in
docs/rfcs/,docs/adrs/,docs/decisions/,docs/architecture/ - If none found, ask the user for a preferred location or default to
docs/adrs/
- Look in
-
Read existing documents to determine:
- Numbering scheme (e.g.,
0001-,ADR-001-, sequential integers) - Template/format used (sections, status values, metadata)
- Style conventions (tone, depth, section order)
- Numbering scheme (e.g.,
-
Calculate the next number in the sequence based on existing documents.
-
Gather context from the user:
- Feature or decision being documented
- Problem statement or motivation
- Constraints and requirements
-
Generate the document using the appropriate template:
RFC Template:
# RFC-{NNN}: {Title} - **Status**: Draft - **Author**: {author} - **Date**: {date} ## Summary ## Motivation ## Detailed Design ## Alternatives Considered ## Migration/Rollout Plan ## Open QuestionsADR Template:
# ADR-{NNN}: {Title} - **Status**: Proposed - **Date**: {date} ## Context ## Decision ## Consequences ### Positive ### Negative ### Neutral -
Write the file and present it to the user for review.
-
Offer to create a git branch for the design doc so it can go through a review process.
Troubleshooting
| Problem | Cause | Solution |
|---|---|---|
| Existing docs not found | Documents live in a non-standard directory | Ask the user for the correct path or search more broadly with find |
| Numbering conflict | Two documents share the same sequence number | Re-scan the directory, pick the next unused number, and flag the conflict |
| Template mismatch | Project uses a custom template that differs from defaults | Read an existing document first and mirror its structure instead of using the built-in template |
Related Skills
shouenlee/task_breakdown
tools
VerifiedTrustedCommunity
Decomposes feature descriptions or GitHub issues into ordered subtasks with file-level scope, acceptance criteria, and optional gh issue create. Use when asked to "break down task", "decompose feature", "create subtasks", "plan implementation", "break this into tasks", "task list", or "implementation plan".
SKILL.mdUpdated Apr 14, 2026
shouenlee/release_notes
documentation
VerifiedTrustedCommunity
Generates changelogs from conventional commits, bumps semantic versions in pyproject.toml or package.json, and publishes GitHub releases. Use when asked to "create release", "release notes", "changelog", "bump version", "semantic version", "tag release", "publish release", or "what changed since last release".
SKILL.mdUpdated Apr 14, 2026
shouenlee/python_lint_fix
development
VerifiedTrustedCommunity
Runs ruff, mypy, and bandit on changed Python files — explains violations and auto-fixes with ruff check --fix. Use when asked to "lint", "fix lint", "check types", "type check", "run mypy", "run ruff", "python quality", or "lint python files".
SKILL.mdUpdated Apr 14, 2026
shouenlee/make_skill_template
development
VerifiedTrustedCommunity
Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.
SKILL.mdUpdated Apr 14, 2026