Fixture. This page is the stdout of
wayfinder skill to-spec, run against a config with tracker value github cli and two registered ticket skills (grill-design, pre-mortem). Change either and this render changes with it.$ wayfinder skill to-spec69 lines
1This 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.
2
3This repo's issue tracker is **github cli**. If you do not know how to operate it, run `wayfinder skill tracker` first.
4
5## Process
6
71. 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.
8
92. 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.
10
11Check with the user that these seams match their expectations.
12
133. 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.
14
15<spec-template>
16
17## Problem Statement
18
19The problem that the user is facing, from the user's perspective.
20
21## Solution
22
23The solution to the problem, from the user's perspective.
24
25## User Stories
26
27A LONG, numbered list of user stories. Each user story should be in the format of:
28
291. As an <actor>, I want a <feature>, so that <benefit>
30
31<user-story-example>
321. As a mobile bank customer, I want to see balance on my accounts, so that I can make better informed decisions about my spending
33</user-story-example>
34
35This list of user stories should be extremely extensive and cover all aspects of the feature.
36
37## Implementation Decisions
38
39A list of implementation decisions that were made. This can include:
40
41- The modules that will be built/modified
42- The interfaces of those modules that will be modified
43- Technical clarifications from the developer
44- Architectural decisions
45- Schema changes
46- API contracts
47- Specific interactions
48
49Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
50
51Exception: 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.
52
53## Testing Decisions
54
55A list of testing decisions that were made. Include:
56
57- A description of what makes a good test (only test external behavior, not implementation details)
58- Which modules will be tested
59- Prior art for the tests (i.e. similar types of tests in the codebase)
60
61## Out of Scope
62
63A description of the things that are out of scope for this spec.
64
65## Further Notes
66
67Any further notes about the feature.
68
69</spec-template>