agentleFS
20030419zhanghongyi20030419zhanghongyi/AI-Software-Engineering-Workflow-Template/.claude/skills/implementation-report/SKILL.md

implementation-report

Skill0 starsChanged 6 months agoMITView on GitHub

Summarize what was implemented before Review Gate.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the plan, diff, commands, and tests.

    line 38
  2. Distinctive:

    Ask for Human Owner review and stop.

    line 42

≈ “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

Implementation Report

Purpose

Generate an Implementation Report after execution.

When to use

  • Implementation work is finished
  • Review Gate is next
  • The user needs a structured execution summary

Read first

  • AI_WORKFLOW.md
  • docs/11_stage_gates.md
  • .ai/artifacts/IMPLEMENTATION_REPORT_TEMPLATE.md
  • Current Plan Artifact

Inputs

  • Plan Artifact
  • git diff
  • Commands run
  • Tests run

Outputs

  • Implementation Report

Steps

  1. Read the plan, diff, commands, and tests.
  2. Confirm what actually changed.
  3. Record files modified, commands run, tests run, plan deviations, and risks.
  4. Fill the Implementation Report.
  5. Ask for Human Owner review and stop.

Human review

Human Owner must review whether the implementation matched the plan and whether risks are acceptable.

Stop conditions

  • Information is insufficient
  • File boundary is unclear
  • Commands or tests were not recorded
  • Plan deviation cannot be explained
  • User has not approved the review step
  • Any action would auto commit / push / merge / release

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.