From pm-delivery
Creates structured technical specification documents bridging product requirements and engineering implementation. Covers problem framing, data model, API design, alternatives, security, testing, and rollout.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-delivery:technical-spec-templateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Write technical specifications that engineers actually read — clear problem framing, unambiguous requirements, explicit decisions, and documented trade-offs.
Write technical specifications that engineers actually read — clear problem framing, unambiguous requirements, explicit decisions, and documented trade-offs.
Ask the user for these if not provided:
Write a tech spec when:
Skip the spec for trivial bug fixes or 1-2 hour changes.
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]
[2–3 sentences. What problem are we solving and why now? No solution language here.]
Goals (in scope):
Non-Goals (explicitly out of scope):
[Any prior art, related systems, or context engineers need to understand the decision space. Link to previous specs, ADRs, or research.]
High-Level Approach: [2–4 sentences describing the chosen solution. Why this approach vs alternatives?]
System Architecture Diagram: [Describe or embed: which services are involved, how data flows, what APIs are called]
Data Model Changes:
-- New tables or schema changes
[Include DDL or schema definition]
API Design:
[Endpoint] [Method]
Request: { [fields and types] }
Response: { [fields and types] }
Error codes: [list]
Key Implementation Details:
| Option | Pros | Cons | Why Rejected |
|---|---|---|---|
| [Alt 1] | [Benefits] | [Drawbacks] | [Reason not chosen] |
| [Alt 2] | [Benefits] | [Drawbacks] | [Reason not chosen] |
| Question | Owner | Due Date | Resolution |
|---|---|---|---|
| [Unresolved question] | [Name] | [Date] | [Pending] |
| Phase | Work | Estimated Effort |
|---|---|---|
| [Phase 1] | [What gets built] | [X days/points] |
| [Phase 2] | [What gets built] | [X days/points] |
| Total | [X story points] |
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-deliveryCreates detailed technical specifications for software projects covering requirements, architecture, APIs, and testing strategies. Use for feature planning, system design docs, or ADRs.
Writes technical specifications for non-trivial engineering changes before implementation. Captures problem statements, goals, proposed solutions, alternatives, and open questions. Based on practices from Stripe, Google, and Notion.
Writes technical specifications for post-decision implementation details including API contracts, database schemas, system architecture, and developer guides.