boss

What This Skill Does

Boss is a comprehensive, full-stack AI orchestration engine for OpenClaw designed to automate the entire software development lifecycle (SDLC) using the BMAD (Boss Method for Agile Development) framework. Instead of performing a single task, the Boss skill acts as a project conductor, delegating specific software engineering roles—including Project Managers, Architects, Designers, Tech Leads, QA Engineers, and DevOps—to different specialized agents. The skill manages the transition between requirements gathering, architecture design, task breakdown, development, rigorous testing, and automated deployment. It operates on a principle of artifact-driven development, ensuring every stage generates verifiable documentation and code outputs before proceeding to the next gate.

Installation

To integrate the Boss agent into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/echovic/boss-skill Ensure your workspace has appropriate write permissions, as the skill needs to create a .boss/ directory to store project artifacts and progress tracking files.

Use Cases

• New Feature Implementation: Automatically add a new module to an existing repository with full test coverage.
• Greenfield Projects: Rapidly bootstrap a new application, from initial design specs to a live, deployed instance.
• Standardized Development: Enforce a consistent R&D workflow across teams by forcing the use of standardized artifacts like PRDs, architectural diagrams, and QA reports.
• Rapid Prototyping: Use the --quick flag to bypass user confirmations for ultra-fast, end-to-end scaffolding.

Example Prompts

1. "Boss mode: build a secure user authentication API service for my existing node project."
2. "/boss start a project to create a task management dashboard with React and FastAPI, make sure to include full unit tests."
3. "Ship it! I need a new feature to handle image uploads for the current app, please handle everything from design to deployment."

Tips & Limitations

• Artifacts are key: The skill relies heavily on the generated markdown files in the .boss/ directory. If the agent stalls, check the latest generated tasks.md to see where the workflow is paused.
• Quality Gates: Do not bypass the quality gate checks (references/quality-gate.md) in a production environment. The QA agent is designed to catch failures before the DevOps agent triggers a deployment.
• Context awareness: The agent performs best when provided with specific constraints in the initial prompt regarding tech stacks or specific library preferences. For existing projects, ensure the agent has read access to your codebase to allow for accurate structure exploration.