increment-planner

What This Skill Does

The sw:increment-planner skill acts as an intelligent orchestration layer for OpenClaw users, designed to streamline the lifecycle of development work within a SpecWeave-initialized project. It automates the bureaucratic overhead of starting new features, bug fixes, or experimental spikes by facilitating the creation of standard documentation structures. Instead of manually scaffolding files, the skill leverages the Template Creator API to generate metadata.json, spec.md, plan.md, and tasks.md in the proper location. By integrating the PM and Architect agent logic into the workflow, it ensures that every increment is tied to a specific project, follows a strict naming convention, and adheres to predefined WIP (Work-in-Progress) limits, preventing context sprawl and project mismanagement.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/anton-abyzov/sw-increment-planner After installation, you can trigger the planner directly using the /sw:increment command, which automatically initiates the pre-flight checks and context resolution.

Use Cases

This skill is essential for any development team using SpecWeave to manage their repository. Key use cases include:

• Feature Development: Rapidly scaffold a new feature while ensuring the project scope and user stories are properly documented.
• Emergency Hotfixes: Quickly initialize a hotfix increment for production issues without violating standard project structure rules.
• Architectural Refactoring: Creating structured plans for technical debt, including specific task breakdowns for implementation.
• Experimental Spikes: Provisioning an experiment folder for proof-of-concept work, ensuring all research is logged and tracked as a distinct increment.

Example Prompts

1. "/sw:increment "Implement OAuth2 Google Login""
2. "/sw:increment "Fix memory leak in data processing service""
3. "/sw:increment "Refactor database connection pool for scaling""

Tips & Limitations

Always use the /sw:increment command instead of invoking the skill directly to ensure that the required pre-flight checks and environment context are correctly loaded. Be mindful of the WIP limits: feature and change-request increments are capped at two, while refactors are limited to one. Do not attempt to spawn additional Task() agents, as this may result in system instability; instead, allow the skill to guide the interaction within the main conversation. Remember that the Project field is mandatory in every spec.md to ensure proper tracking.