Skip to content
Skills Library
Management & product · Writing

spec

/spec

Use when settled decisions must be written as a project-local feature acceptance contract with traceable, machine-verifiable criteria. Not for interviewing an ambiguous request or implementing code.

Repository
ezpowers ↗
Licence
MIT
Last repository change
18.10.2026

Assessment and security

95/ 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.
Content30 / 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
3
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 18.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

Use when settled decisions must be written as a project-local feature acceptance contract with traceable, machine-verifiable criteria. Not for interviewing an ambiguous request or implementing code.

Original author description

Use when settled decisions must be written as a project-local feature acceptance contract with traceable, machine-verifiable criteria. Not for interviewing an ambiguous request or implementing code.

How it works

  1. Load and inspect
  2. Write and validate
Original SKILL.md headings · 56 lines, 362 words
SKILL.md preview
---
name: spec
description: Use when settled decisions must be written as a project-local feature acceptance contract with traceable, machine-verifiable criteria. Not for interviewing an ambiguous request or implementing code.
disable-model-invocation: true
---

# Spec

Convert settled decisions into a feature acceptance contract. This is narrower
than general specification writing: `deep-interview` can clarify ambiguous
intent inside the current conversation; an explicitly invoked `spec` records
what this project must prove before a feature is complete.

## Load and inspect

Read `.ezpowers/contracts/spec-contract.md` and
`.ezpowers/contracts/verification-contract.md`; they are the source of truth
for artifact shape, managed markers, fields, identifiers, and validation. If
the local kit is absent, route to `setup`.

Read settled decisions from the current conversation, repository instructions,
the registered documentation graph when present, `CONTEXT.md`, relevant ADRs,
architecture and frontend-design artifacts, every applicable nearest
`DESIGN.md`, existing specs, public entry points, and tests. Treat local wiki
candidates as hints only and verify them
against repository sources. If a material product decision remains open, stop
and recommend an explicit `deep-interview` invocation rather than interviewing
inside `spec`. Return to `design-architecture` when implementation would
otherwise invent a boundary, data flow, lifecycle, deployment, or verification
decision.

## Write and validate

Create one feature spec under `docs/specs/`. Keep purpose, scope, settled
requirements, exclusions, risks, and design references in readable Markdown.
Include `Architecture impact: none` with evidence or name the settled canonical
architecture paths and decision IDs. Return to `design-architecture` if that
impact is not settled; do not defer a boundary decision to implementation.
Add exactly one managed JSON block using the canonical spec contract. Every
criterion must be binary, observable, host-independent, and traceable to one
requirement. Mark real boundary-crossing behavior as integration evidence and
include failure criteria when rejection behavior is part of the requirement.
For a planning-profile project, state the observable business or artifact
outcome without prescribing a file-format parser; `prepare-execute` maps each
criterion to both one logical deliverable and a real project-owned check.
Every new spec records `design_context`: UI work names the broad frontend
artifact and all mapped `DESIGN.md` files; non-UI work records `required:
false` with a reason. Do not treat a legacy spec's missing field as a template
for new work.

Run:

```text
python .ezpowers/ezpowers.py validate --spec <spec-path> --json
```

Validation failure or an unresolved material decision is blocking. Report the
spec path, requirement-to-criterion mapping, integration criteria, exclusions,
design references, and remaining risks. Continue to `prepare-execute` only
with a valid spec.
Files in this package (3)
  • SKILL.md 3 KB
  • agents/openai.yaml 1 KB
  • agents/project-openai.yaml 1 KB

Versions

RepositoryScoreLicence
This page · dlwlgus9125/ezpowers95MIT
renzrollon/interlock100MIT
CodaColaLight/nightmill100Apache-2.0
duronext/jig100MIT
optiflowic/keyturn100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
rjmurillo/ai-agents100MIT
flavien-ia/hypervibe-craft100Apache-2.0

Database snapshot: 13.11.2026 · package version 76e06c28e3e9 (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

  • 90write-spec
    Write a feature design spec with numbered acceptance criteria before any plan or code. Use when starting any feature, or when a request is too vague to build without guessing.
  • 100product-owner
    Interviews the user one topic at a time to turn raw requirements or an issue into a SPEC.md with user stories, acceptance criteria, edge cases and out-of-scope items, on a new feature or fix branch. Use when the user wants to spec, scope or define a feature or bug fix, write…
  • 95strata.spec
    Use when a feature or change needs its requirements, acceptance criteria and constraints written or revised before planning; when a planning document exists but has no desired specification; when the user says what to build, acceptance criteria, requirements, or asks whether the…
  • 100seed
    Use when goal, constraints, and success criteria are already settled and the user wants them frozen into a formal spec an agent can execute and verify: 'turn this into a spec', 'write it up as a Seed', or right after an interview. Returns an immutable Seed with acceptance…
  • 100to-spec
    Use when settled conversation decisions need synthesis into an agent-ready implementation spec, stopping before publication. Not for turning plans into tickets: use to-tickets.
  • 100scope
    This skill should be used when a task needs its scope contract written or changed, for example "define scope", "write acceptance criteria", "what does this task have to do", "add a non-goal", "add a criterion", "change the contract", or "scope this task". It runs a conversation…

Feedback and reports

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