plan-do-review-renew

Coordinate multi-session task workflows from triage to handoff.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/ANaka/work-cycle --skill plan-do-review-renew
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-do-review-renew
Source: https://github.com/ANaka/work-cycle/tree/main/skills/plan-do-review-renew
Command: npx skills add https://github.com/ANaka/work-cycle --skill plan-do-review-renew

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated end-to-end task workflow from triage to handoff, ensuring explicit checkpoints and cross-cutting gates across planning, execution, and review.

Core Features & Use Cases

  • Triage with tiered verification and scope capture.
  • Brainstorming and design exploration when needed.
  • Plan, execute, test, review, and merge with a defined gate-based flow, including durable artifacts in a worktree.
  • Handoff prompts and external-review options for cross-model collaboration.

Quick Start

Kick off a new task and start triage to begin the plan-do-review-renew cycle.

Frequently Asked Questions about plan-do-review-renew

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

FAQPage Schema
How do I coordinate end-to-end task workflows across multiple planning and execution sessions?

End-to-end task workflows across multiple sessions are coordinated using a structured plan-do-review-renew cycle with explicit checkpoints, gating, and cross-session checkpointing. This ensures phases like triage, execution, and review maintain state continuity.

What is the best way to manage a multi-phase software feature from brainstorming to PR review?

Managing a multi-phase feature from brainstorming to PR review requires a gate-based flow that enforces durable design artifacts within a git worktree. This structure separates planning, execution, testing, and merge strategy into verifiable stages.

How do I maintain task state and design artifacts when handing off work between different models?

Task state and design artifacts are maintained during handoff using durable artifacts stored in a worktree alongside generated handoff prompts. This enables cross-model collaboration by providing explicit context and external-review options for the next session.

Does this task lifecycle management approach work for complex refactors that require extensive design exploration?

Yes, task lifecycle management supports complex refactors by integrating tiered verification and scope capture during triage. It applies brainstorming and design exploration before execution, ensuring the refactor plan is validated through defined gates.

When should I use a structured plan-do-review cycle instead of a standard linear development workflow?

A structured plan-do-review cycle should be used instead of a linear workflow when tasks involve multi-phase requirements like bugs or features needing explicit gating, durable design artifacts, and cross-session checkpointing to prevent state loss between sessions.