agentleFS
wedabrowedabro/bro-skills/.agents/skills/speckit.implement/SKILL.md

speckit.implement

Skill3 starsChanged 45 days agoMITView on GitHub

Code Builder (Anti-Regression) - Deploy code in tasks with IRONCLAD protocols.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 3

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Read .agents/specs/[feature]/tasks.md, plan.md, spec.md, and .agents/memory/constitution.md.

    line 10
  2. Distinctive:

    Verify after every task with targeted tests, linters, or type checks.

    line 23
  3. Distinctive:

    All task acceptance criteria met, targeted and suite tests pass with zero regression, task checkbox marked, and atomic conventional commit …

    line 26
  4. Distinctive:

    Never commit failing code.

    line 29

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

Mission

Execute approved implementation tasks atomically, safely, and test-first while enforcing anti-regression gates, deviation rules, and runtime consistency.

Inputs and Outputs

  • Read .agents/specs/[feature]/tasks.md, plan.md, spec.md, and .agents/memory/constitution.md.
  • Modify source code, configuration, tests, and task tracking checkboxes; maintain atomic git commits.

Protocol

  1. Respect the 15-Minute Rule: each task must be atomic, touching at most 3 files with verifiable acceptance criteria.
  2. Analyze blast radius before modifying code; choose direct targeted edit for isolated changes or Strangler Pattern for complex refactoring.
  3. Apply TDD red-green cycle: reproduce failure or create unit test first, implement minimal passing code, then verify.
  4. Re-anchor context against constitution.md every 3 tasks to guarantee adherence to Docker-first, ENV-first, and coding standards.
  5. Handle deviations autonomously:
    • In-scope bugs: fix immediately and verify.
    • Missing critical files/configs: add with documented rationale.
    • Blockers: perform systematic root cause analysis before escalating.
    • Architectural shifts: STOP and request explicit user confirmation.
  6. Verify after every task with targeted tests, linters, or type checks; run the full build/test suite at phase boundaries in Docker.

Completion Gate

All task acceptance criteria met, targeted and suite tests pass with zero regression, task checkbox marked, and atomic conventional commit created.

Guard Rails

Never commit failing code. Never hardcode secrets, tokens, or environment values. Never exceed task scope without updating plan or tasks.

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.