mattpocock/to-spec

This skill takes the current conversation context and codebase understanding and produces a spec (you may know this document as a PRD). Do NOT interview the user — just synthesize what you already know.

The issue tracker and triage label vocabulary should have been provided to you — run /setup-matt-pocock-skills if not.

Process

Explore the repo to understand the current state of the codebase, if you haven't already. Use the project's domain glossary vocabulary throughout the spec, and respect any ADRs in the area you're touching.
Sketch out the seams at which you're going to test the feature. Existing seams should be preferred to new ones. Use the highest seam possible. If new seams are needed, propose them at the highest point you can. The fewer seams across the codebase, the better - the ideal number is one.

Check with the user that these seams match their expectations.

Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label - no need for additional triage.

Problem Statement

The problem that the user is facing, from the user's perspective.

Solution

The solution to the problem, from the user's perspective.

User Stories

A LONG, numbered list of user stories. Each user story should be in the format of:

As an , I want a , so that

This list of user stories should be extremely extensive and cover all aspects of the feature.

Implementation Decisions

A list of implementation decisions that were made. This can include:

The modules that will be built/modified
The interfaces of those modules that will be modified
Technical clarifications from the developer
Architectural decisions
Schema changes
API contracts
Specific interactions

Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.

Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it within the relevant decision and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.

Testing Decisions

A list of testing decisions that were made. Include:

A description of what makes a good test (only test external behavior, not implementation details)
Which modules will be tested
Prior art for the tests (i.e. similar types of tests in the codebase)

Out of Scope

A description of the things that are out of scope for this spec.

Further Notes

Any further notes about the feature.

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Safety

85

Quality

85

Clarity

88

Completeness

72

Summary

This skill converts an ongoing conversation and project codebase understanding into a structured specification (PRD) and publishes it to the project's issue tracker. It does NOT interview the user but synthesizes existing knowledge, explores the repo to understand context, proposes test seams, and writes a comprehensive spec covering problem, solution, user stories, implementation decisions, testing strategy, scope, and further notes.

Detected Capabilities

read repository structure and codebasesynthesize conversation contextgenerate structured specification documentsinteract with issue tracking systemsapply labels/triage tags to issuesaccess project configuration and glossaries

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

write project specgenerate prdpublish to issue trackersynthesize requirementsdocument feature scope

Use Cases

Generate project specs from conversation history
Convert informal requirements into formal PRDs
Publish specifications to issue trackers
Document implementation and testing decisions
Establish feature scope and out-of-scope items
Propose test architecture seams before development

Quality Notes

Clear, well-structured template provided that matches PRD best practices
Explicit instruction to avoid interviewing the user and focus on synthesis only
Good guidance on architectural decisions (preferring existing seams, minimizing test seams)
Template emphasizes external behavior testing over implementation details
Requires prior `/setup-matt-pocock-skills` setup which establishes vocabulary and ADRs
Clear warnings about not including file paths or code snippets to avoid outdated specs
Exception for prototypes is well-defined and includes guidance on trimming to decision-rich content
Template is comprehensive but well-organized with clear section purposes
Guidance on using domain glossary vocabulary and respecting ADRs shows attention to project standards

Model: claude-haiku-4-5-20251001Analyzed: Jul 9, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

to-spec