z1nun

buildcrew

Run the full buildcrew feature pipeline — plan, adversarial challenge, design, implement, QA, review, coherence audit. Use when the user asks to build, add, or implement a feature and wants the structured multi-agent lifecycle instead of ad-hoc coding.

buildcrew-debug

Root-cause debugging with the buildcrew investigator — 4-phase investigation (investigate, analyze, hypothesize, implement) verified by QA. Use when the user reports a bug, error, stack trace, or asks why something is broken.

Testing & QA Listed

buildcrew-qa

QA a project with buildcrew quality roles — browser QA via Playwright, 3-lens QA audit on git diffs, or a 0-10 code health score. Use when the user asks to test the site, audit code quality, run QA, or get a health check.

buildcrew-review

Review with buildcrew reviewer roles — code review with auto-fix, pre-code architecture review, or UX/design review with 0-10 scoring. Use when the user asks for a code review, PR review, architecture review, or design/UX review.

buildcrew-security

Run a buildcrew security audit — OWASP Top 10 + STRIDE threat modeling with a fix loop for critical findings. Use when the user asks for a security audit, vulnerability scan, or security check.

buildcrew-ship

Ship with the buildcrew shipper — pre-flight tests, version bump, changelog, commit, push, PR creation. Use when the user asks to ship, release, deploy, push, or create a PR.

buildcrew-think

Product thinking with the buildcrew thinker — 6 forcing questions that test whether something is worth building, ending in a design doc. Use when the user has a product idea, asks "is this worth building", or wants to think a concept through before code.