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.

Use the configured issue tracker and triage label vocabulary. If missing, use /setup-matt-pocock-skills when available; otherwise ask only for the configuration needed to publish. Follow the project’s conventions for readiness and publication.

Process

1. 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.

1. 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.

Reuse testing decisions already agreed in the conversation or established by the project. Record any proposed new seams as unresolved decisions; ask only if a consequential missing decision prevents a useful spec. Do not re-interview the user or invent an approval.

1. Write the spec using the template below, then publish it to the project issue tracker. Apply the ready-for-agent triage label unless the configured project workflow calls for a different spec status — no additional triage is needed solely because this skill produced it.

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 numbered list of user stories covering the agreed scope. Each user story should be in the format of:

1. As an , I want a , so that

1. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending

Cover the agreed behavior and consequential edge cases without adding requirements merely to lengthen the spec. Distinguish confirmed decisions from open questions.

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.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: waffleflopper
• Source: waffleflopper/ai-tools
• License: MIT

Install and usage instructions live in the source repository linked above.