to-spec
/to-spec
Zamienia bieżącą rozmowę w specyfikację i publikuje ją w trackerze projektu bez wywiadu, z samej syntezy tego co ustalono.
- Autor
- maximechbt ↗
- Repozytorium
- skills ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 29.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 29.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Zamienia bieżącą rozmowę w specyfikację i publikuje ją w trackerze projektu bez wywiadu, z samej syntezy tego co ustalono.
Wyzwalacze z opisu
Oryginalny opis (EN)
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what was already discussed. Use for /to-spec, \"write the spec\", or after a grilling session when the user wants the result recorded as an issue.
Jak działa
- Process
- Problem Statement
- Solution
- User Stories
- Implementation Decisions
- Testing Decisions
- Out of Scope
- Further Notes
Podgląd SKILL.md
--- name: to-spec description: "Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what was already discussed. Use for /to-spec, \"write the spec\", or after a grilling session when the user wants the result recorded as an issue." --- This skill takes the current conversation context and codebase understanding and produces a spec. Do NOT interview the user; just synthesize what you already know. The issue tracker and triage label vocabulary should have been provided to you. If not, tell the user to run `/setup-modemax`. ## 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 `ready-for-agent` triage label - no need for additional triage. <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. 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. </spec-template>
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · maximechbt/skills | 100 | MIT |
| h2xd/skills | 100 | MIT |
| hachemsoft/ia-toolkit | 100 | MIT |
| sammcj/agentic-coding | 100 | Apache-2.0 |
| VladButacu/agentkit | 100 | MIT |
| lttr/claude-marketplace | 100 | MIT |
| OutlineDriven/outline-driven-development | 100 | Apache-2.0 |
| FradSer/dotclaude | 100 | MIT |
| vinvcn/mattpocock-skills-zh-cn | 96 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 70d101747446 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 1 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100to-prd
Zamienia kontekst bieżącej rozmowy w PRD i publikuje go w trackerze zgłoszeń projektu. - 100to-prd
Zamienia kontekst bieżącej rozmowy w PRD i publikuje go w trackerze zgłoszeń projektu. - 100to-prd
Zamienia kontekst bieżącej rozmowy w PRD i publikuje go w trackerze zgłoszeń projektu. - 96to-prd
Zamienia bieżący kontekst rozmowy w PRD i publikuje go w trackerze zgłoszeń projektu. - 100to-feature-spec
Zamienia ustalenia z rozmowy i wiedzę o kodzie w specyfikację funkcji lub PRD, bez nowego wywiadu o wymaganiach. - 100to-prd
Zamienia bieżącą rozmowę w szkic PRD i publikuje go w narzędziu do zgłoszeń dopiero po wyraźnym zatwierdzeniu.