Coordinate a 12-stage adaptive development workflow from research to deployment.
npx skills add https://github.com/artemiimillier/bulletproof --skill bulletproof
Please help me install this Agent Skill. Skill: bulletproof Source: https://github.com/artemiimillier/bulletproof/tree/main Command: npx skills add https://github.com/artemiimillier/bulletproof --skill bulletproof
Bulletproof provides a disciplined, repeatable process to manage AI-driven software work, preventing chaotic coding and unfinished tasks by enforcing a 12-stage workflow from research to deployment.
Run the bulletproof skill via Claude Code to activate the 12-stage workflow for your non-trivial coding task.
High-intent search queries and answers about installing and using this skill.
To prevent chaotic coding and unfinished tasks, you can enforce a rigorous 12-stage AI development workflow with strict stage gates, anti-rationalization checks, and fresh-context handoffs. This ensures verifiable, reliable delivery from research to deployment.
A fresh-context handoff is a process mechanism in AI development workflows where task context is reset or managed between stages. It works alongside 40% context window guardrails to maintain reasoning quality and prevent context degradation during complex coding tasks.
You can manage complex feature development and refactors by applying an adaptive 12-stage workflow that guides AI agents step-by-step through research, spec, planning, phased implementation, self-audit, verification, impact analysis, and deployment.
Yes, this 12-stage workflow is explicitly designed for complex bug fixes and architectural changes across software projects. It enforces deterministic progress checks, security scans, and integration checks to verify reliable delivery before moving forward.
The best way to stop AI scope creep is to implement anti-rationalization guardrails that detect incomplete work and require justification and evidence before advancing. Strict stage gates ensure the AI agent remains within the defined task scope.
You should not use a rigid 12-stage workflow for trivial or minor coding adjustments, as the strict stage gates, fresh-context handoffs, and mandatory verification checks are designed specifically for non-trivial software tasks and complex architectural changes.
lihaoze123Initialize coding sessions by loading project context and routing workflows.
Michae2xlMonitor deployed web applications for performance regressions and console errors.
lengoctuong2005Automate pre-commit code review with security scans, tests, and fixes.
BrunoAMSilvaCoordinate multiple subagents with isolated context and two-stage reviews.
