mohitagw15856/pm-claude-skills/technical-spec-template

-- New tables or schema changes
[Include DDL or schema definition]

[Endpoint] [Method]
Request: { [fields and types] }
Response: { [fields and types] }
Error codes: [list]

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]

Dimension	0	5	10
Problem framing	Problem statement is the solution restated ("we need a queue"), or missing; no non-goals	Problem stated but with solution language leaking in; non-goals present but generic ("out of scope: everything else")	Problem described in user/business terms with numbers, independent of any solution; goals measurable; ≥2 non-goals that shut down real scope assumptions
Decision documentation	One approach, no alternatives — a design description, not a decision record	Alternatives table exists but strawmanned (cons-only options nobody argued for); rejection reasons are taste, not evidence	≥2 genuine alternatives with honest pros, evidence-based rejection reasons, recorded dissent where it exists, and revisit triggers for contested calls
Security & privacy depth	Section skipped or "N/A" on a feature that touches user data	Boilerplate answers (encrypt at rest/in transit) with no analysis of this feature's specific data exposure	Data touched is enumerated, the design's single largest privacy risk is named, authn/authz/compliance addressed concretely, and unresolved risks visibly gate approval
Operational readiness	No testing plan, rollout plan, or rollback trigger; open questions absent or all "TBD"	Testing and rollout sketched but rollback is untested intent; some open questions lack owners or dates	Tests cover the tricky edge cases, rollout is staged with progress criteria, rollback trigger is concrete (and doesn't strand data), and every open question has a named owner and due date

technical-spec-template

Summary

SKILL.md

Technical Spec Template Skill

Required Inputs

When to Write a Tech Spec

Technical Spec Output Format

Technical Specification — [Feature Name]

1. Problem Statement

2. Goals & Non-Goals

3. Background & Context

4. Proposed Solution

5. Alternative Approaches Considered

6. Security & Privacy Considerations

7. Performance & Scalability

8. Testing Plan

9. Rollout Plan

10. Open Questions

11. Implementation Timeline (Rough)

Guidelines

Deeper Materials

Scoring Rubric (0–40)

Quality Checks

Anti-Patterns

Related skills