Skip to content
cccskills
FreePublished on GitHub

agent-loop

Orchestrates a multi-agent loop involving planning, development, review, and publishing sub-agents to implement and publish features test-first and with high standards compliance.

The English summary is being prepared. Showing the original description.

larchanka/skills30 stars(GitHub 30 + cccskills 0)
Works withGitHub

Run score Not tested

See how to install

Files included (2)

  • SKILL.md4.6 KB
  • README.md8.2 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Multi-Agent Iteration Loop

This skill coordinates four independent agents (planning, development, review, and publisher) in a continuous loop to deliver and publish spec-compliant, standard-abiding features.

graph TD
    Start["User Request / Spec"] --> Plan["1. Planning Subagent"]
    Plan --> SavePlan["Generate tasks/plan.md & todo.md"]
    SavePlan --> ApprPlan{"User Approval?"}
    ApprPlan -- No --> Plan
    ApprPlan -- Yes --> Dev["2. Development Subagent"]
    Dev --> ImpTask["Implement Next Task via TDD"]
    ImpTask --> Rev["3. Review Subagent"]
    Rev --> Check{"Any Findings?"}
    Check -- Yes (Bug / Smell) --> Dev
    Check -- No --> CheckMore{"More Tasks?"}
    CheckMore -- Yes --> Dev
    CheckMore -- No --> Pub["4. Publisher Subagent"]
    Pub --> OpenPR["Create Branch, Commit & gh pr create"]
    OpenPR --> Done["Done - Pull Request Published"]

Workflow Execution Steps

[!IMPORTANT] Coordinator Constraint: The coordinator agent executing this skill MUST NOT write implementation code, create source files, or modify files in the codebase directly during the development phase. The coordinator is solely responsible for planning, orchestrating the loop, conducting code reviews, and managing publishing. All code changes and task implementations MUST be delegated to the spawned subagents.

1. Planning Phase

  • Spawn the planning subagent to read the user request/specification and codebase structure.
  • The planning agent will output tasks/plan.md (architecture, design, tasks) and tasks/todo.md (checkbox todo list).
  • Once the plan is saved, present it to the user for feedback and approval.

2. Development Phase (Task Implementation)

  • Select the first incomplete task from tasks/todo.md.
  • Spawn the development subagent to implement that task.
  • The development agent must:
    • Operate incrementally, writing a failing unit test first.
    • Implement only enough code to pass the test.
    • Verify compile checks and execution results.
    • Update the status of the task in tasks/todo.md to completed [x].

3. Review Phase (Quality Gates)

  • Spawn the review subagent to perform standard and spec audits on the branch's git diff.
  • The review agent outputs findings under ## Standards and ## Spec headers.
  • Evaluate results:
    • If there are findings (e.g., hard violations or baseline smells):
      • Send a message to the development subagent containing the reviewer's report.
      • Instruct the developer to resolve the bugs or smells.
      • Rerun the review agent once the developer has updated the branch.
    • If there are 0 findings:
      • Check tasks/todo.md for the next incomplete task.
      • If tasks remain, loop back to Step 2.
      • If all tasks are completed, proceed to Step 4.

4. Publishing Phase (Deployment Gate)

  • Spawn the publisher subagent to automate the integration and deployment lifecycle.
  • The publisher agent must:
    • Verify git status and stage all changed files.
    • Commit files using the Conventional Commits syntax and push to origin.
    • Execute gh pr create with standard metadata titles/descriptions to open the GitHub Pull Request.
    • Return the direct URL link to the Pull Request.

Exit Criteria

  • All tasks in tasks/todo.md are marked [x].
  • The review agent reports 0 standard violations or spec omissions.
  • All unit and integration tests in the test suite pass successfully.
  • The publisher agent has successfully pushed and opened a GitHub Pull Request, sharing its URL.

Sub-Agent Skill References

To ensure execution consistency, each sub-agent in this loop is dedicated to executing a specific workspace skill. They must load and re-use the following guides:

  • Planning Sub-Agent:
  • Development Sub-Agent:
  • Review Sub-Agent:
    • Primary Skill: code-review (performs two-axis checks for standard compliance and specification compliance).
  • Publisher Sub-Agent:
    • Primary Skill: pull-request (automates git checkout, commits, pushes, and GitHub CLI PR creation).

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

The English summary is being prepared. Showing the original description.

larchanka/skills30Updated Oct 27, 2026

Generates comprehensive AI context, AGENTS.md, and structured documentation in a context/ directory for any brownfield codebase using Tree-sitter AST extraction, dependency analysis, predefined python scripts, and orchestrated subagents.

The English summary is being prepared. Showing the original description.

larchanka/skills30Updated Oct 27, 2026

Manual browser testing and automation using Chrome DevTools MCP server. Handles port management, app launch, browser automation, login, and end-to-end testing.

The English summary is being prepared. Showing the original description.

larchanka/skills30Updated Oct 27, 2026

Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.

The English summary is being prepared. Showing the original description.

larchanka/skills30Updated Oct 27, 2026

Progressively investigate PRs, commits, releases, and project evolution. Start with a lightweight assessment, dynamically deepen analysis based on complexity and risk, use subagents for independent investigations, and maintain evidence-backed project knowledge.

The English summary is being prepared. Showing the original description.

larchanka/skills30Updated Oct 27, 2026

Creates a new feature branch from current git changes, commits them, pushes to the remote, and opens a github pull request using the `gh` cli. Use this skill when asked to create a github pull request

The English summary is being prepared. Showing the original description.

larchanka/skills30Updated Oct 27, 2026

See all skills by larchanka

Report a problem with this skill