agentleFS
Sign inStart free
mustafahasanainmustafahasanain/frappe-workflow/skills/task-implementation/SKILL.md

task-implementation

Skill0 starsChanged 3 months agoMITView on GitHub

Execute the approved TASK_PLAN.md step by step - status updates, per-step validation, blocker recording, the implementation summary, and the completion gate before Codex review.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. yuanJewel/skills★ 2same name
    2. ItsSidhartha/claude-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository8 other files it gives its agents.

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:

    All steps Completed and the completion gate passes → hand to the codex-review skill (review action).

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Task Implementation Skill

Executes the approved plan during the implementation stage (and applies fixes during review_fixes). One step at a time, validated before marked done.

When to Use

  • Stage implementation: next non-completed plan step.
  • Stage review_fixes: applying validated Codex findings (the codex-review skill decides what; this skill governs how edits are made and validated).

Inputs

  • docs/ai-context/TASK_PLAN.md (authoritative step list and statuses).
  • Workflow state (aggregate counts, blockers).
  • The repository.

Outputs

  • Implemented, validated changes; step statuses updated in the plan; state counts synced (total_steps / completed_steps / blocked_steps).
  • docs/ai-context/implementation-summary.md (template: templates/review/IMPLEMENTATION_SUMMARY.md) when all steps complete.

Procedure

Per-step loop: references/implementation-loop.md. Validation rules: references/step-validation.md. Gate before review: references/completion-gate.md.

Preconditions

  • Stage is implementation or review_fixes; plan validates.

Stopping Conditions

  • All steps Completed and the completion gate passes → hand to the codex-review skill (review action).
  • A step blocks → record it (plan + state blocker add), keep stage implementation, report to the user. Do not continue past a blocking dependency.

Prohibited

  • Marking a step Completed before its validation succeeded.
  • Skipping a step silently, or marking partial work complete.
  • Updating docs/ai-context/FEATURE_CHANGELOG.md (finalization-only).
  • Unrecorded deviation from the plan: small technical deviations that preserve the objective are documented in the summary; business scope changes stop the work and go back to planning with the user's awareness.
  • Reading the whole repository — read only files the current step needs.

Shared Rules

shared-workflow-rules.md, error-and-blocker-handling.md, git-safety-rules.md.

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