agentleFS
Sign inStart free
lucastosettolucastosetto/dev-skills/skills/spec/SKILL.md

spec

Skill0 starsChanged 25 days agoMITView on GitHub

Write an implementation spec for a feature or bug fix from a ticket or requirements, or, in rfc mode, a structured RFC for others to review (context, goals, proposal, alternatives, risks, rollout). Use on "write a spec", "plan the implementation", "how should we build this", "create an RFC", "design doc", "/spec", "/spec rfc".

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

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 145 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Follow ../../shared/policy.md.

    line 13
  2. Very specific:

    Use an existing context.md for this ticket if there is one.

    line 16
  3. Distinctive:

    Read the code the context maps.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 145 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

Follow ../../shared/policy.md. Run dev-skills:project-profile if not loaded this session.

1. Context

Use an existing context.md for this ticket if there is one; otherwise run dev-skills:gather-context first.

2. Choose the approach

Read the code the context maps. Consider the realistic options (usually 1-3). Pick the one that solves the requirement at the root with the smallest change that fits the codebase's existing patterns; reuse what already exists.

  • autonomous / balanced: decide and record why in the spec.
  • guided: present the options with trade-offs and a recommendation; wait for the choice.

3. Write it

Save spec.md next to context.md.

Default mode (for the developer):

# Spec — <TICKET> <title>
## Approach
<what and why, 3-6 lines>
## Changes
- `path` — <change>
## Data / migrations
## API / contract changes
## Flags and rollout
## Risks and edge cases
## Testing
<pointer to qa-plan.md, or the test cases if small>
## Assumed

Omit empty sections.

rfc mode (for reviewers): same research, more structure and less code detail: Context · Problem · Goals / Non-goals · Proposal (with a diagram when flows or components change) · Alternatives considered (and why not) · Risks and mitigations · Rollout and rollback · Testing strategy · Open questions · Timeline/effort. Save as rfc.md. Publishing it to Notion/Confluence/Docs goes to the confirmation list.

4. QA plan

Unless the caller says otherwise, run dev-skills:qa-plan on the spec.

In guided, show the spec and QA plan and wait for approval before returning. Otherwise return the paths and a 5-line summary.

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