agentleFS
joaoajmatosjoaoajmatos/ze/.claude/skills/speckit-process-after-implement/SKILL.md

speckit-process-after-implement

Skill2 starsChanged 47 days agoUnlicenseView on GitHub

Checks that a finished phase reads Implemented everywhere. Use when speckit finishes implementing and the after_implement hook fires.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    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. Very specific:

    When every task is ticked, spec.md Status, the AGENTS.md phase row and the specs/README.md row must all say Implemented.

    line 14

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

After implement: check phase status

Tick each finished task in tasks.md in the commit that finishes it. Then run:

python3 scripts/process/check_phase_status.py specs/phases/NNN-name

When every task is ticked, spec.md Status, the AGENTS.md phase row and the specs/README.md row must all say Implemented. The check exits 1 and names the one that does not. Fix it in the same commit; do not report the phase as done while it fails.

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.