Agent skill · sammcj
to-spec
Turn the current conversation context into a spec and submit it as a GitHub issue. Use when user wants to create a spec or PRD from the current context.
What it needs
About 2k tokens when loaded.
What this skill does
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 synthesise what you already know. 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. 2. 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. 3. Write the spec using the template below, then publish it to the project issue tracker. Apply the needs-triage triage label so it enters the normal triage flow. <spec-template> 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: 1. As an <actor>, I want a <feature>, so that <benefit> <user-story-example> 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 </user-story-example> 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. Testing Decisions A list of testing decisions that were made. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sammcj/to-spec--c24cb8