solo-build

What This Skill Does

The solo-build skill acts as the primary execution engine for OpenClaw AI, designed to transition projects from the planning phase into concrete implementation. Unlike generic coding skills, solo-build is strictly bound to a TDD (Test-Driven Development) workflow. It automatically detects, parses, and executes tasks defined in your docs/plan/ directory. By enforcing project-specific workflows defined in docs/workflow.md and verifying git hooks before every commit, it ensures that your codebase remains consistent, clean, and fully tested as you implement features.

Installation

To add this skill to your workspace, run the following command in your terminal:

clawhub install openclaw/skills/skills/fortunto2/solo-build

Once installed, ensure your project structure includes a docs/ folder. The skill will automatically attempt to locate your implementation plan at docs/plan/. If you are using a new project, ensure your stack configuration exists in templates/stacks/ so the skill can correctly identify and verify your environment's pre-commit hooks.

Use Cases

• Continuous Implementation: Use this when a developer has finalized a roadmap in plan.md and wants the AI to handle the tedious, task-by-task coding process.
• Strict TDD Enforcement: Use this in environments where code quality is non-negotiable; the skill forces a write-test-before-code pattern.
• Refactoring & Feature Additions: When working on complex tasks that require multiple commits and verification steps, solo-build manages the state of the task list to ensure nothing is missed.
• Automation of Git Hygiene: Automatically handles pre-commit hook installation and execution, preventing the need for manual linting or testing runs before pushing code.

Example Prompts

1. "Build it. Follow the plan in docs/plan/user-auth-track/plan.md and start with the first task."
2. "Start building. Please skip ahead and execute task 3.2 from the active implementation plan."
3. "Implement tasks for the payment gateway integration track. Let's get this finished."

Tips & Limitations

• Pre-flight Checks: Always ensure docs/workflow.md is populated if your team uses custom linting or specific integration testing commands. Without this, the skill defaults to moderate TDD settings.
• No Scaffolding: Remember that solo-build is for implementation. Do not point this skill at a blank directory; use /scaffold first to generate your boilerplate.
• Task Jumps: Utilize the --task X.Y flag to resume work after an interruption or to perform targeted debugging on a specific section of your implementation plan.