Skip to content
Skills Library
Programming · Planning

spec-first

/spec-first

Turn a feature request into testable acceptance criteria and a small implementation plan before editing. Use when requirements are ambiguous, a task spans several files, or a change may affect existing behavior.

Licence
MIT
Last repository change
30.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 30.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Turn a feature request into testable acceptance criteria and a small implementation plan before editing. Use when requirements are ambiguous, a task spans several files, or a change may affect existing behavior.

Original author description

Turn a feature request into testable acceptance criteria and a small implementation plan before editing. Use when requirements are ambiguous, a task spans several files, or a change may affect existing behavior.

How it works

  1. Outcome
  2. Procedure
  3. Deliverable
  4. Boundaries
Original SKILL.md headings · 29 lines, 216 words
SKILL.md preview
---
name: spec-first
description: Turn a feature request into testable acceptance criteria and a small implementation plan before editing. Use when requirements are ambiguous, a task spans several files, or a change may affect existing behavior.
license: MIT
---

# Spec First

## Outcome
A compact implementation brief that makes the requested behavior observable and defines what must remain unchanged.

## Procedure
1. Restate the requested outcome in plain language. Separate the user's goal from any proposed implementation.
2. Inspect the relevant code and docs before proposing changes. Reuse repository conventions where possible.
3. List acceptance criteria that can be checked through tests, commands, UI behavior, logs, or documented output.
4. Record non-goals and compatibility constraints. Call out assumptions that would materially change the design.
5. Identify the smallest safe change set. Group files into implementation, tests, and docs.
6. Define verification in advance: the targeted test, broader regression checks, and any manual check that cannot be automated.
7. For a large task, split work into independent slices with a clear integration point. Do not create artificial subtasks for a trivial change.

## Deliverable
Use a short brief:
- Goal
- Acceptance criteria
- Non-goals
- Key files and design choice
- Risks / assumptions
- Verification plan

## Boundaries
- Ask a focused question only when a missing decision blocks safe progress. Otherwise state a reversible assumption and continue.
- Do not silently broaden scope or redesign unrelated systems.
- Planning is not permission to deploy, spend money, contact people, or make destructive changes.

Versions

RepositoryScoreLicence
This page · voyager67/AgentFieldkit90MIT
natsaros7/specter81MIT

Database snapshot: 13.11.2026 · package version 9dd802b68a7d (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100writing-acceptance-criteria
    Use when a spec document has been approved during brainstorming and you need to produce testable acceptance criteria before writing the implementation plan - converts spec requirements into a structured acceptance criteria document
  • 90spec-driven-development
    Turn a feature, bug fix or risky change into a short spec with EARS acceptance criteria and a task list before writing code, then build in small verified steps. Use when starting any non-trivial feature, a change that touches data, auth, money or a public contract, or when the request is ambiguous.
  • 100intent-driven-development
    Turn ambiguous or high-impact product and engineering changes into scoped, verifiable acceptance criteria before or alongside implementation. Use when a user asks to clarify a feature, define acceptance criteria, de-risk a security/data/migration/integration change, prepare…
  • 100spec-planning
    Spec-first planning: task breakdown, measurable acceptance criteria, dependency order, risk priority. crew-planner applies it; the plan goes to docs/PLAN.md. Use when the scope is unclear or the work spans more than one change.
  • 90Spec
    Writes a grounded spec: recalls prior decisions from LTM, explores the affected code, then writes testable acceptance criteria to specs/<feature>.md. Use when the user asks to 'spec this', 'write a spec', 'define what to build', or 'write requirements / acceptance criteria'…
  • 100spec
    Turn a problem into testable requirements with acceptance criteria, through a first-principles gate, a memory-first prior-art gate, and a PRD schema. Use when you say `spec this out`, `what should we build`, or `define the requirements`, and run it before plan. Do NOT use to…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.