echovic/boss-skill
Overview
This skill orchestrates a fully automated software development pipeline using a multi-agent BMAD approach. It coordinates specialist agents (PM, Architect, UI, Tech Lead, Scrum Master, Developers, QA, DevOps) to take a request from requirement to deployment and deliver staged artifacts. Triggers include natural phrases like "boss mode", "/boss", "build this", "ship it", and variants for new projects or feature additions.
How this skill works
When triggered, the skill asks brief intake questions (new project vs existing, interface type, constraints) unless run in quick mode. It then runs a four-stage pipeline: planning (PM, Architect, UI), review and task breakdown (Tech Lead, Scrum Master), development and continuous validation (frontend/backend agents, testing, QA), and deployment (DevOps), saving artifacts into a .boss/<feature>/ folder. Flags allow skipping UI or deployment stages or running without confirmation checkpoints.
When to use it
- Start a new project end-to-end with minimal manual coordination
- Add a new feature to an existing codebase and need full lifecycle delivery
- Automate repetitive delivery work across PM, design, engineering, QA, and DevOps
- Generate standard artifacts (PRD, architecture, tasks, QA and deploy reports) for compliance or handover
- Run a controlled, reproducible pipeline with quality gates and test-first discipline
Best practices
- Provide clear intake answers: new vs existing repo, desired interface, and constraints
- Use --quick only for prototypes; confirm checkpoints for production work
- Enable UI stage for user-facing features and skip it for API/CLI-only projects
- Keep tests and QA mandatory: pipeline enforces quality gates before deploy
- Store feature name and context to keep .boss/<feature>/ artifacts organized
Example use cases
- Bootstrapping a new web service: generate PRD, architecture, UI specs, tasks, tests, and deploy
- Adding an API endpoint to an existing backend with automated tests and CI deployment
- Shipping a small feature end-to-end for a startup with minimal project management overhead
- Running a hands-off demo build using --quick to skip confirmations for speed
- Delivering repeatable artifacts and reports for audit or client handoff
FAQ
Common triggers include phrases like "boss mode", "/boss", "build this", "ship it", "start a project", and similar commands indicating end-to-end development.
Can I skip UI design or deployment?
Yes. Use --skip-ui to omit UI design for API/CLI projects and --skip-deploy to stop before deployment.
What happens if tests fail?
The pipeline enforces a quality gate: failed tests block deployment and require remediation before progressing.
