Double729 Plansuite

What This Skill Does

PlanSuite is a structured workflow management system for OpenClaw that enforces a rigorous 'Plan-Freeze-Execute' lifecycle for complex tasks. It moves project management out of the transient chat context and into persistent, file-based structures. By utilizing three core files—task_plan.md, progress.md, and findings.md—it ensures that projects have a clear roadmap, milestone tracking, and a recorded history of decisions and failures.

This skill is designed for high-stakes automation where 'winging it' leads to technical debt or broken states. It enforces status transitions, requiring users to explicitly finalize a plan before allowing execution, and dictates strict documentation standards for progress updates and troubleshooting logs.

Installation

To add PlanSuite to your OpenClaw agent, use the official clawhub command in your terminal:

clawhub install openclaw/skills/skills/double729/double729-plansuite

Use Cases

PlanSuite is ideal for:

• Large-scale refactoring: Where you need to track dependencies and sub-plans.
• Infrastructure automation: Managing sequential deployment steps with checkpoints.
• Multi-stage data processing: Where each step produces an output that must be verified against predefined criteria before proceeding.
• Long-running research projects: Keeping track of experiments, results, and 'dead ends' across multiple sessions.

Example Prompts

1. "PlanSuite, let's start a new project to migrate our backend API to FastAPI. Please initialize the template files in the current directory and help me define the initial milestones."

2. "I've updated the task_plan.md with the latest architecture changes. Please review the sub-plans, and once I give the signal, mark it as FINALIZED so we can begin the implementation."

3. "We've hit a roadblock in Milestone 2. Please document the current failure in findings.md, suggest a change to the implementation plan, and set the status to DRAFT so we can pivot."

Tips & Limitations

• Strict Workflow: PlanSuite is intentionally restrictive. If you are doing simple, single-turn tasks, this skill will add unnecessary overhead. Use it for projects requiring persistence.
• Session Isolation: Always use the suggested sessions_spawn to keep the implementation environment clean. This prevents the primary chat context from getting cluttered with shell command outputs or transient logs.
• Change Control: Resist the urge to edit code during execution if it contradicts the plan. Always update the findings.md first to maintain auditability.
• File Maintenance: The system relies on these files for state recovery. Ensure they are not deleted or moved during the project lifecycle, as the agent uses them as the 'source of truth' to resume tasks after restarts.