AGENT SKILL

to-spec

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.

License 许可
MIT
最近更新
2026-11-15
Stars
★ 0
Forks
0

01 前言 Front Matter

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

02 资源文件 2

03 SKILL.md 正文

A prompt or brief naming this skill is its invocation.

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.

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.

Reuse recorded test-seam decisions and plan approval with their dates and quoted words. Gather missing code facts and record seam evidence for review. Before proposing an unanswered decision, read and apply the contribution guide's Triage inference test, inferred-list and owner-question rules.

  1. Write the spec using the template below. Copy every relied-on owner decision with its date and quoted words into the issue-facing contract; private records are not required inputs. Publish one specification issue in the repository containing most of the work, reading .repo-standards/rules/comments.md#disclaimers first on a hosted tracker. Cross-repository tickets remain children of that one specification. Use the guide's direct-body-contract publication route. Return the exact published contract and factual/test-seam evidence to the orchestrating agent for its split decision and acceptance under the guide's Triage and Readiness sections and the installed parent-readiness rules.

Return the published specification's link and exact revision to the caller, which starts or resumes its ticket-publication step. For an amendment under the guide's Triage rules, consume the amendment grill's decisions, revise the specification and return its link and revision for the caller's delta-ticket step and the guide's acceptance process.

<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>

Reads

Paths are relative to the repository root.

  • docs/agents/issue-tracker.md and docs/agents/triage-labels.md: the issue tracker and its triage label vocabulary. When the tracker config is missing and no tracker was provided, ask the user where to publish the spec; when the label config is missing, use the canonical role names as the label strings.
  • .repo-standards/rules/comments.md: the installed comment rules, whose section the posting steps name. When it is missing, post issue bodies and comments as the steps describe.
  • GLOSSARY.md and the ADRs in docs/adr/: the domain vocabulary and decisions to respect. When either is missing, use the codebase's own words.
  • The installed rules, such as the github-repository-configuration rules, which the repository-standards skill looks up: the companion labels readiness needs. When they are missing, readiness carries no companion labels.
  • CONTRIBUTING.md: Triage inference, publication, amendments and readiness. If missing, use grilling's missing-guide fallback, independent exact-revision review and the tracker rules provided; route unresolved owner choices to the user without repeating recorded answers.
  • The grilling skill: the inference fallback, only when the contribution guide is missing. If also missing, report it and stop for the missing policy.

04 同仓库更多 Skills