mcpField
S
system-execution-report

system-execution-report

github.com/coleam00Agent workflows722213 installsUpdated 3w ago
Repository

About system-execution-report

system-execution-report is a skill for reviewing completed software implementation and writing an execution report. It records validation results, implementation outcomes, challenges, plan deviations, and recommendations in a designated directory.

Key features

  1. 01Reviews completed implementation
  2. 02Documents differences between plan and outcome
  3. 03Records syntax, type, and test validation
  4. 04Lists added and modified files and line changes
  5. 05Provides recommendations for future work

Use cases

  1. 01Document implementation after a feature is completed
  2. 02Summarize test and static-check results
  3. 03Analyze why implementation diverged from plan
  4. 04Inform future planning and development practices

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/coleam00/skills --skill system-execution-report

After installing, type/system-execution-reportin Claude Code to confirm it loaded.

Details

From the project README

Execution Report

Review and deeply analyze the implementation you just completed.

Context

You have just finished implementing a feature. Before moving on, reflect on:

  • What you implemented
  • How it aligns with the plan
  • What challenges you encountered
  • What diverged and why

Generate Report

Save to: .claude/execution-reports/[feature-name].md

Meta Information
  • Plan file: [path to plan that guided this implementation]
  • Files added: [list with paths]
  • Files modified: [list with paths]
  • Lines changed: +X -Y
Validation Results
  • Syntax & Linting: ✓/✗ [details if failed]
  • Type Checking: ✓/✗ [details if failed]
  • Unit Tests: ✓/✗ [X passed, Y failed]
  • Integration Tests: ✓/✗ [X passed, Y failed]
What Went Well

List specific things that worked smoothly:

  • [concrete examples]
Challenges Encountered

List specific difficulties:

  • [what was difficult and why]
Divergences from Plan

For each divergence, document:

[Divergence Title]

  • Planned: [what the plan specified]
  • Actual: [what was implemented instead]
  • Reason: [why this divergence occurred]
  • Type: [Better approach found | Plan assumption wrong | Security concern | Performance issue | Other]
Skipped Items

List anything from the plan that was not implemented:

  • [what was skipped]
  • Reason: [why it was skipped]
Recommendations

Based on this implementation, what should change for next time?

  • Plan skill improvements: [suggestions]
  • Execute skill improvements: [suggestions]
  • CLAUDE.md additions: [suggestions]

Comments

Markdown supported