agentleFS
Sign inStart free
mrlemoosmrlemoos/galicia/.agents/skills/spec/SKILL.md

spec

Skill1 starsChanged 7 days agoMITView on GitHub

Synthesises agreed discussion into local change specification. Use when user requests spec, PRD, or implementation handoff.

171 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

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 148 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Prefer existing highest useful behavioural test seam.

    line 10
  2. Very specific:

    Write docs/specs/<slug>.md unless repo prescribes another local path.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 148 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Spec

Synthesise existing discussion; no new interview. Read relevant context.md, docs/Language.md, domain context, ADRs, current behaviour. Mark missing decisions explicitly; never invent agreement. No emojis.

Prefer existing highest useful behavioural test seam. Confirm seam with user unless already agreed. New seam: explain need. Cover distinct user outcomes, edge cases, failures; skip repetitive story boilerplate.

Write docs/specs/<slug>.md unless repo prescribes another local path. Status: draft, active, complete, superseded, or abandoned. Include owner/domain, related ADRs, tickets, superseded-by when relevant.

Sections: problem; intended behaviour; acceptance checks; implementation decisions/contracts; test seam + commands/prior art; exclusions; unresolved decisions. Paths useful for navigation; avoid brittle implementation recipes. Prototype snippet only when clearer than prose; label provenance.

Recommend breakdown when change spans independently verifiable slices, substantial migration, or exceeds fresh agent context. Small coherent change stays single spec. Never manufacture ticket count threshold.

Consequential durable tradeoff: recommend ADR + scoped small-model research/review subagent, e.g. Luna/Haiku if available. Spawn only when authorised. Domain definitions belong in Language.md, not framework glossary.

Local Markdown only. Preserve existing files; revise deliberately, never overwrite unrelated spec. No tracker publishing. Completion needs acceptance evidence; age never proves staleness. Preserve decision rationale through linked ADRs before proposing spec deletion; deletion always explicit approval.

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