qte77/plugins/docs-generator/skills/generating-tech-spec
plugins/docs-generator/skills/generating-tech-spec/SKILL.md
--- name: generating-tech-spec description: Generates structured technical specifications including ADR (MADR), RFC, design documents, and proposals. Use when writing a spec, creating an ADR, drafting an RFC, or creating a design document. compatibility: Designed for Claude Code metadata: allowed-tools: Read, Write, Glob, Grep, WebSearch, WebFetch argument-hint: [spec-type] [topic] stability: stable content-hash: sha256:71c2abb97fa7b7e910c41f19caed62a94b59b49f66730b5aff2e8ef6ebc8a4ee l
$ install --global
skillsauthnpx skillsauth add qte77/claude-code-plugins plugins/docs-generator/skills/generating-tech-specInstall 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 17, 2026, 11:29 AM4.8s2 files scanned
SKILL.md
- name:
- generating-tech-spec
- description:
- Generates structured technical specifications including ADR (MADR), RFC, design documents, and proposals. Use when writing a spec, creating an ADR, drafting an RFC, or creating a design document.
- compatibility:
- Designed for Claude Code
- allowed-tools:
- Read, Write, Glob, Grep, WebSearch, WebFetch
- argument-hint:
- [spec-type] [topic]
- stability:
- stable
- content-hash:
- sha256:71c2abb97fa7b7e910c41f19caed62a94b59b49f66730b5aff2e8ef6ebc8a4ee
- last-verified-cc-version:
- 1.0.34
Technical Specification Generation
Target: $ARGUMENTS
Generate a structured technical specification document based on the requested type and topic.
References (MUST READ)
Read these before proceeding:
references/tech-spec-formats.md— ADR (MADR), RFC, design doc, and proposal templates
Spec Types
| Type | Trigger phrases | Output directory |
|------|----------------|-----------------|
| ADR | "adr", "architectural decision record" | docs/adr/ |
| RFC | "rfc", "request for comments" | docs/rfc/ |
| Design Doc | "design doc", "design document", "tech spec" | docs/specs/ |
| Proposal | "proposal", "technical proposal" | docs/specs/ |
Workflow
- Detect spec type from arguments — default to Design Doc if ambiguous
- Read reference for the matching template format
- Glob for existing specs in the target directory to determine next sequence number:
- ADR:
docs/adr/NNNN-*.md(four-digit, e.g.,0001-use-postgres.md) - RFC:
docs/rfc/NNNN-*.md - Design Doc/Proposal:
docs/specs/<date>-<slug>.md
- ADR:
- WebSearch for relevant context if the topic references specific technologies
- Generate the document using the appropriate template structure
- Output location and suggest next steps (review, share, link to implementation)
Output Naming
ADR: docs/adr/NNNN-<slug>.md (e.g., 0003-use-event-sourcing.md)
RFC: docs/rfc/NNNN-<slug>.md (e.g., 0001-api-versioning.md)
Design: docs/specs/<date>-<slug>.md (e.g., 2026-03-01-auth-redesign.md)
Proposal: docs/specs/<date>-<slug>.md (e.g., 2026-03-01-migrate-to-k8s.md)
Rules
- Always read existing specs first to match formatting and numbering conventions
- Include YAML frontmatter with title, date, status, and author fields
- ADRs must follow MADR format (Context → Decision → Consequences)
- RFCs must include a "Status" field (Draft → Proposed → Accepted/Rejected)
- Never overwrite existing spec files — always create new ones
- Use
converting-doc-formatskill for PDF/HTML/DOCX export
Related Skills
qte77/writing-readme
documentation
VerifiedTrustedCommunity
Generate or update README.md files across three scopes — repo (with project-type detection), account (GitHub user profile), and org (organization profile). Use when creating, updating, or aligning a README to org conventions.
1SKILL.mdUpdated Apr 19, 2026
qte77/auditing-readme
development
VerifiedTrustedCommunity
Audit README.md files against best practices for repos, accounts, or orgs. Detects missing sections, stale links, inconsistent formatting, and convention violations. Use when reviewing README quality across one or many repos.
1SKILL.mdUpdated Apr 19, 2026
qte77/researching-website-design
development
VerifiedTrustedCommunity
Analyzes industry websites for design patterns, layout, typography, and content strategies using first-principles thinking. Use when researching website design, UI patterns, or competitive design analysis.
1SKILL.mdUpdated Apr 18, 2026
qte77/auditing-website-usability
development
VerifiedTrustedCommunity
Audits website usability for UX optimization, covering forms, navigation, validation, and microcopy. Use when reviewing user experience, task completion flows, or interface friction points.
1SKILL.mdUpdated Apr 18, 2026