agentleFS
Sign inStart free
skullninjaskullninja/coco-workflow/skills/execute/SKILL.md

execute

Skill7 starsChanged 2 months agoMITView on GitHub

Execute the next available tracked task with TDD, pre-commit validation, PR workflow, AI code review, and issue tracker bridge sync. Primary execution interface for multi-session feature work.

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

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 1

    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:

    Run the /coco:execute command.

    line 23
  2. Distinctive:

    Commit with issue key traceability

    line 31

“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

Coco Execute Skill

This skill delegates to the /coco:execute command, which implements the full 15-step TDD execution loop with PR workflow, AI code review, and issue tracker bridge sync.

When to Use

  • Implementing a feature that has been imported into the coco tracker as an epic
  • Executing tasks from a specs/{feature}/tasks.md that has been converted to tracked tasks
  • Any multi-session work where dependency tracking matters

Alternatives

  • For single-issue hotfixes or quick changes, use the hotfix skill instead
  • For autonomous execution until epic completion, use /coco:loop

Execution

Run the /coco:execute command. It handles:

  1. Pre-execution gate (tracker + issue tracker verification)
  2. Dependency-aware task selection via coco-tracker ready
  3. Issue branch creation (if pr.enabled)
  4. Issue tracker bridge (start: "In Progress")
  5. TDD implementation (RED -> GREEN -> verify)
  6. Pre-commit validation (UI change detection)
  7. Commit with issue key traceability
  8. PR creation with issue ID (if pr.enabled)
  9. AI code review via code-reviewer agent
  10. Review-fix loop (max 3 iterations)
  11. PR merge (if pr.enabled)
  12. Tracker task close
  13. Issue tracker bridge (complete: "Done" at PR merge)
  14. Acceptance criteria verification
  15. Next task check (loop or report completion)

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