technical-spec-template
Create structured technical specification documents that bridge product requirements and engineering implementation. Use when writing a tech spec, engineering spec, system design doc, or API specification. Produces a complete spec with problem statement, proposed solution, data model, API design, alternatives considered, security considerations, testing plan, and rollout strategy.
npx skills add mohitagw15856/pm-claude-skills --skill technical-spec-template --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Technical Spec Template Skill Write technical specifications that engineers actually read — clear problem framing, unambiguous requirements, explicit decisions, and documented trade-offs. ## Required Inputs Ask the user for these if not provided: - **Feature or system description** (what needs to be specced) - **Related PRD or product brief** (if available) - **Engineering reviewers** (whose sign-off is needed) - **Known constraints** (technical limitations, security requirements, performance targets) ## When to Write a Tech Spec Write a tech spec when: - The feature requires changes to 2+ systems - There are significant architectural decisions to make - More than one engineer will work on the implementation - The feature has security, privacy, or compliance implications - Estimated effort is >5 story points Skip the spec for trivial bug fixes or 1-2 hour changes. --- ## Technical Spec Output Format ### Technical Specification — [Feature Name] **Author:** [Name] **Status:** Draft | In Review | Approved | Implemented **Created:** [Date] | **Last Updated:** [Date] **Reviewers:** [Eng Lead, Architect, PM, Security if needed] **Related PRD:** [Link] | **Jira Epic:** [Link] --- #### 1
- Required Inputs
- When to Write a Tech Spec
- Technical Spec Output Format
- Technical Specification — [Feature Name]
- Guidelines
- Deeper Materials
- Scoring Rubric (0–40)
- Quality Checks
- Anti-Patterns
What does the technical-spec-template skill do?
Create structured technical specification documents that bridge product requirements and engineering implementation. Use when writing a tech spec, engineering spec, system design doc, or API specification. Produces a complete spec with problem statement, proposed solution, data model, API design, alternatives considered, security considerations, testing plan, and rollout strategy.
How do I install it?
Run `npx skills add mohitagw15856/pm-claude-skills --skill technical-spec-template --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From mohitagw15856/pm-claude-skills, a repository with 1,255 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.