Generating Tech Spec
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.
Install
$ agentstack add skill-qte77-claude-code-plugins-generating-tech-spec ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-qte77-claude-code-plugins-generating-tech-spec) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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/-.md
- 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-.md (e.g., 0003-use-event-sourcing.md)
RFC: docs/rfc/NNNN-.md (e.g., 0001-api-versioning.md)
Design: docs/specs/-.md (e.g., 2026-03-01-auth-redesign.md)
Proposal: docs/specs/-.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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: qte77
- Source: qte77/claude-code-plugins
- License: Apache-2.0
- Homepage: https://qte77.github.io/claude-code-plugins/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.