agentleFS
Sign inStart free
PatriotAgenticLLCPatriotAgenticLLC/better_claude_skillz/skills/execute/SKILL.md

execute

Skill3 starsChanged 4 months agoMITView on GitHub

Execute an implementation plan

57 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use context-optimize, ralplan 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.
  • ibahgatSkill

    context-optimize

    Improve context efficiency and cache stability for long or complex sessions.

    Also in 3 projects that use this

  • ibahgatSkill

    ralplan

    Create a strict, quality-first execution plan with explicit gates and rollback-ready sequencing.

    Also in 5 projects that use this

  • Yeachan-HeoSkill

    ultragoal

    Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

    Also in 4 projects that use this

  • buddyhSkill

    deep-dive

    Deep dive on any topic. Decomposes into subtopics, researches each in parallel with thorough source gathering, then synthesizes into a comprehensive report (4,000-10,000+ words, 40-100+ sources). Scales depth dynamically based on topic complexity. Use when asked for a deep dive, deep research, comprehensive analysis, or thorough investigation of a topic.

    Also in 4 projects that use this

  • mukcoSkill

    principles

    General software engineering principles — DRY, SOLID, YAGNI, KISS, naming, code smells, and refactoring. Language-agnostic. Use alongside language-specific skills.

    Also in 3 projects that use this

  • team-attentionSkill

    compound

    This skill should be used when the user says "/compound", "compound this", "document learnings", "save what we learned", or after completing a PR. Extracts knowledge from PR context and saves to docs/learnings/.

    Also in 3 projects that use this

  • +1 more from ibahgat

The file

Show its rules and text

We split this skill into the rules it gives an agent

20 rules. 0 are common, 19 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 19

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

    Read plan file: $ARGUMENTS

    line 11
  2. Distinctive:

    Read the ENTIRE plan carefully

    line 17
  3. Distinctive:

    Read existing related files if modifying

    line 28
  4. Distinctive:

    Follow the detailed specifications exactly

    line 31
  5. Distinctive:

    Add structured logging where appropriate

    line 34
  6. Distinctive:

    After each file change, check syntax

    line 37
  7. Distinctive:

    Ensure imports are correct

    line 38
  8. Distinctive:

    Verify types are properly defined

    line 39
  9. Distinctive:

    After completing implementation tasks:

    line 43
  10. Distinctive:

    Create all test files specified in the plan

    line 45
  11. Distinctive:

    Follow the testing approach outlined

    line 47
  12. Distinctive:

    Ensure tests cover edge cases

    line 48
  13. Distinctive:

    If any command fails:

    line 58
  14. Distinctive:

    All tasks from plan completed

    line 67
  15. Distinctive:

    All tests created and passing

    line 68
  16. Distinctive:

    All validation commands pass

    line 69
  17. Distinctive:

    If you encounter issues not addressed in the plan, document them

    line 107
  18. Distinctive:

    If you need to deviate from the plan, explain why

    line 108
  19. Distinctive:

    If tests fail, fix implementation until they pass

    line 109
  20. Distinctive:

    Don't skip validation steps

    line 110

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

Execute: Implement from Plan

Plan to Execute

Read plan file: $ARGUMENTS

Execution Instructions

1. Read and Understand

  • Read the ENTIRE plan carefully
  • Understand all tasks and their dependencies
  • Note the validation commands to run
  • Review the testing strategy

2. Execute Tasks in Order

For EACH task in "Step by Step Tasks":

a. Navigate to the task

  • Identify the file and action required
  • Read existing related files if modifying

b. Implement the task

  • Follow the detailed specifications exactly
  • Maintain consistency with existing code patterns
  • Include proper type hints and documentation
  • Add structured logging where appropriate

c. Verify as you go

  • After each file change, check syntax
  • Ensure imports are correct
  • Verify types are properly defined

3. Implement Testing Strategy

After completing implementation tasks:

  • Create all test files specified in the plan
  • Implement all test cases mentioned
  • Follow the testing approach outlined
  • Ensure tests cover edge cases

4. Run Validation Commands

Execute ALL validation commands from the plan in order:

# Run each command exactly as specified in plan

If any command fails:

  • Fix the issue
  • Re-run the command
  • Continue only when it passes

5. Final Verification

Before completing:

  • All tasks from plan completed
  • All tests created and passing
  • All validation commands pass
  • Code follows project conventions
  • Documentation added/updated as needed

6. Archive the Completed Plan

After successful verification:

  • Move the plan file to plans/archive/ (create the directory if it doesn't exist)
  • Example: plans/2026-03-01-feature.md -> plans/archive/2026-03-01-feature.md
  • Active plans/ should only contain pending or in-progress plans

Output Report

Provide summary:

Completed Tasks

  • List of all tasks completed
  • Files created (with paths)
  • Files modified (with paths)

Tests Added

  • Test files created
  • Test cases implemented
  • Test results

Validation Results

# Output from each validation command

Ready for Commit

  • Confirm all changes are complete
  • Confirm all validations pass
  • Ready for /commit command

Notes

  • If you encounter issues not addressed in the plan, document them
  • If you need to deviate from the plan, explain why
  • If tests fail, fix implementation until they pass
  • Don't skip validation steps

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