Essentials
Conversation to Spec
Listed under Product PlanningRequirements Definition
Summary
Synthesize the current discussion and codebase context into a publishable specification and write it into the project's issue tracker. Input is existing conversation; output is a problem statement plus spec body. Suited to defining requirements documents.
Why we picked it Why recommended
SkillPouch records why this skill was curated, stage by stage.
-
T10.s2Define requirements
Turns clarified needs into an executable spec and user-story skeleton.
How to use Applicable stages
Use it in these workflow stages. Open a stage to return to its task.
Get and review
App deep-link installation is coming soon. Open the upstream repository to inspect the skill today.
Check the sources Evidence & sources
Public links you can open and verify on your own.
Upstream source
- Upstream repository (mattpocock/skills) ↗ Verified on 2026-10-28
Boundaries Known limitations
By default does not re-interview users; thin context yields thin specs. Publishing issues depends on a configured tracker.
Identity and license
License, review date, repository path, and stable identifier.