nessar/vac-optimizer
1
0 Fork 0
Code Issues 7 Pull Requests 4 Actions Packages Projects 1 Releases Wiki Activity

update skills

Browse Source
This commit is contained in:
nessar committed 2026-09-25 10:00:00 +02:00
1 parent 9fb18f57ec
commit ff86cf48b4
82 files changed
+2156 -650
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

.agents/skills/to-spec/SKILL.md
+8 -9
View File
@@ -1,22 +1,21 @@
---
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 you've already discussed.
disable-model-invocation: true
description: Synthesize the current conversation into a development spec, with optional publication to the configured tracker when requested.
---
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.
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.
The issue tracker and triage label vocabulary should have been provided to you — run `/setup-matt-pocock-skills` if not.
Read the configured tracker and triage vocabulary only when publication is requested. A local draft does not require tracker setup.
## 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.
2. Describe how acceptance criteria can be verified using existing behavior-level tests where possible. Choose boundaries that exercise the actual risks, not a predetermined seam count. Distinguish agreed decisions from proposals and unresolved requirements.
Check with the user that these seams match their expectations.
Use the discussion's existing decisions. Record remaining uncertainty; ask only when a consequential missing decision prevents a useful spec, rather than restarting an interview.
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.
3. Write the requested spec using the template below as appropriate. Publish only if the user asked for publication; otherwise return the draft or save it at their selected path. Use the configured tracker and triage labels, marking it `ready-for-agent` only when actionable. On an ambiguous create failure, check for duplicates before retrying; if access is unavailable, preserve the draft and report the limitation.
<spec-template>
@@ -30,7 +29,7 @@ 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:
A concise set of user stories or acceptance criteria covering the agreed behavior. When user stories help, use:
1. As an <actor>, I want a <feature>, so that <benefit>
@@ -38,7 +37,7 @@ A LONG, numbered list of user stories. Each user story should be in the format o
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.
Cover the requested behavior and important failure cases without inventing scope to fill the template.
## Implementation Decisions