agentleFS
Sign inStart free
MetaMindTeamMetaMindTeam/ssot-kit/.claude/skills/spec/SKILL.md

spec

Skill1 starsChanged 4 months agoApache-2.0View on GitHub

Entry point from a brief or intent to a working spec. Use when you have a client brief / task / idea and want the spec-driven cycle to pick it up. Triggers: "/spec <brief-file>", "I have a brief", "here is a spec", "start from this brief", "spec this", "turn this into a spec".

168 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use backprop, ios-clean and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JuliusBrusseeSkill

    backprop

    Bug → spec protocol. When a bug is found or a test fails, trace the cause, decide whether a new §V invariant would catch recurrence, append to §B. This is the one non-obvious thing SDD does that plan-then-execute doesn't. Triggers on test failure, bug report, post-mortem, or explicit user ask.

    Also in 4 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 5 projects that use this

  • Saqlain-811Skill

    ios-fix

    Autonomous iOS bug fixer. (gstack)

    Also in 5 projects that use this

  • bastosSkill

    ios-design-review

    Review iOS app UI/UX design quality using Apple's design principles and the Liquid Glass-era design language from WWDC25/26. Use when asked for a design review, UX critique, visual design assessment, or evaluation of an app's interface quality, design intent, alignment with the new Apple design system, or usability. Triggers: "design review", "UX review", "visual design critique", "review the UI", "does this design work", "evaluate this interface", "design feedback", "Liquid Glass review".

    Also in 5 projects that use this

  • ShreyRaviSkill

    plan-tune

    Self-tuning question sensitivity + developer psychographic for gstack (v1: observational). Review which AskUserQuestion prompts fire across gstack skills, set per-question preferences (never-ask / always-ask / ask-only-for-one-way), inspect the dual-track profile (what you declared vs what your behavior suggests), and enable/disable question tuning. Conversational interface — no CLI syntax required.

    Also in 7 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 6 projects that use this

  • +2 more from Saqlain-811

The file

Create a free account to mount
Files
SKILL.md

spec — from brief to spec (router)

Turns a brief/intent into the spec-driven cycle. This skill routes to the right entry point by project state — so a brief never dead-ends on an unknown command.

Route by state

  1. Read the brief (the file/text passed with the command).
  2. Detect project state:
    • CLAUDE.md has <...> placeholders, or spec/domain/entities.yaml holds only the Example stub, or spec/features/ has only kit modules → empty project → run init-project (stack choice → SSOT scaffold → generators), then author the feature spec.
    • Project already initialized (spec canon present) → run new-feature: derive spec/features/<slug>/spec.yaml from the brief (entities, API, invariants, acceptance criteria).
  3. Do not write code here. This skill produces/updates the spec only. Implementation follows the canon (approved spec → TDD), see spec/standards/spec_driven_standard.md.

Brief → spec extraction (both routes)

From the brief pull, and record in the spec:

  • Entities + fields → spec/domain/entities.yaml
  • Invariants (the hard rules — "never", "must", "rejected") → spec/domain/invariants.yaml. For a money/ledger domain, always include the implicit checklist even if the brief omits it: no-negative-balance · append-only · integer-minor-units · idempotent-writes · audit-trail · concurrency-safe. (A brief that says "this is money, we'll try to break it" implies all of these.)
  • API surface → spec/api/openapi.yaml
  • Acceptance criteria (how the client verifies) → the feature spec's acceptance: block.

Why the implicit checklist: a spec-driven cycle narrows to the letter of the brief. For money domains the unwritten invariants (idempotency, audit) are what "breaking it seriously" targets — surface them at spec time, not after a failed acceptance run.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free