sisyphus-implementation-guide

Define Sisyphus agent execution flow with phase-based subtask processing and quality checks.

Updated Jan 8, 2026
One-click install
npx skills add https://github.com/takemo101/compose-workflow --skill sisyphus-implementation-guide
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sisyphus-implementation-guide
Source: https://github.com/takemo101/compose-workflow/tree/main/.opencode/skill/sisyphus-implementation-guide
Command: npx skills add https://github.com/takemo101/compose-workflow --skill sisyphus-implementation-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive, step-by-step guide and strict rules for the Sisyphus agent to execute code implementation tasks, ensuring adherence to defined phases, responsibilities, and quality checks.

Core Features & Use Cases

  • Structured Implementation Flow: Defines a clear, phased process from issue reception to code merging.
  • Subtask Management: Automates the detection, handling, and sequential implementation of subtasks within an issue.
  • Quality Gates: Enforces critical checks like code size, design consistency, and review scores before proceeding.
  • Role Separation: Clearly delineates responsibilities between Sisyphus and container-workers.
  • Use Case: When assigned a complex coding task (issue), Sisyphus will automatically break it down into manageable subtasks, create separate branches and PRs for each, ensure each subtask meets quality standards through automated checks and reviews, and finally merge them all to close the parent issue.

Quick Start

Follow the detailed implementation flow and phase responsibilities outlined in this guide when executing coding tasks.

Frequently Asked Questions about sisyphus-implementation-guide

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate agentic workflow for multi-phase code implementation?

To automate agentic workflow, this guide defines a Sisyphus agent execution flow with subtask detection, environment setup, TDD, quality reviews, and automated merging to enforce strict phase-based responsibilities.

How does subtask management work for complex coding issues?

Subtask management automatically detects, handles, and sequentially implements subtasks within an issue, creating separate branches and PRs for each before merging them to close the parent issue.

Can I enforce quality assurance checks before merging code in an agentic workflow?

Yes, you can enforce quality assurance through built-in quality gates that check code size, design consistency, and review scores before proceeding to the automated merging phase.

What is the best way to separate role boundaries in an automated code workflow?

The best way to separate roles is by delineating responsibilities between the Sisyphus agent and container-workers, which optimizes token consumption and prevents common implementation errors.

Does this implementation guide support TDD and automated phase-based processing?

Yes, the implementation guide enforces strict adherence to a multi-phase process that explicitly includes environment setup, test-driven development (TDD), and quality reviews as mandatory steps.

When should I not use a structured implementation flow for code tasks?

You should avoid this structured implementation flow for simple coding tasks that do not require subtask breakdown, multi-phase quality gates, or automated PR management overhead.