SuperAPI AI Directory

to-spec

Coding & development

View repository

Updated 10-16 09:45

About this skill

This skill uses the current conversation context and codebase understanding to produce a spec.Do notinterview the user, only synthesize what you already know.

The issue tracker and triage label vocabulary should already be provided to you; if not, ask the user to run /setup-matt-pocock-skills。

Process

  1. If you have not yet explored the repo, explore it first to understand the current state of the codebase. Always use the project domain glossary vocabulary in the spec, and follow the relevant ADRs.

  2. Draft which seams you plan to test this feature at. Prefer existing seams over new seams. Use the highest-level seam possible. If you really do need new seams, propose them at the highest level possible.

The fewer seams the better, ideally one. Confirm with the user that these seams meet expectations.

  1. Write the spec using the template below, and publish it to the project issue tracker. Apply the ready-for-agent triage label; no additional triage is needed.

Problem Statement

The problem the user is facing, described from the user's perspective.

Solution

The solution to the problem, described from the user's perspective.

User Stories

A very long numbered list of user stories. Each user story uses the following format:

  1. As an , I want a , so that

This user stories list should be very complete, covering all aspects of the feature.

Implementation Decisions

A list of implementation decisions that have been made. It can include:

  • Modules to build/modify
  • Module interfaces to modify
  • Technical clarifications from the developer
  • Architectural decisions
  • Schema changes
  • API contracts
  • Specific interactions

Do not include specific file paths or code snippets. They can quickly become outdated.

Exception: if a snippet produced by a prototype encodes a decision more precisely than prose (state machine, reducer, schema, type shape), it can be inlined into the relevant decision, with a brief note that it comes from the prototype. Keep only the decision-dense parts, do not include a complete working demo.

Testing Decisions

A list of testing decisions that have been made. Include:

  • A description of what a good test is (test only 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 what is out of scope for this spec.

Further Notes

Other notes about the feature.