What problem does it solve?
One-shot LLM planning produces walls of text that get lost between sessions and hide architectural flaws until implementation. This Skill turns an idea into a deeply structured, file-based system blueprint that survives context resets and is linted for gaps before any code is written.
Core Features & Use Cases
- Phased planning workflow: Runs intake, mandatory web research, vision/architecture drafting, component breakdown, data modeling, and decomposition into roughly 38 executable action points with dependency graphs.
- Persistent planning wiki: Maintains a
blueprint/ markdown knowledge base with SESSION.md, NEXT.md, journal, and ADR decision logs so work resumes cleanly after /clear or crashes.
- Lint and adversarial review: Runs lint passes after every phase to catch gaps, contradictions, and uncited claims, with optional multi-agent setups (Researcher, Curator, Linter, Auditor) for Claude Code users.
- Use Case: A developer pastes a SaaS product idea and asks for a full implementation plan; the Skill produces an interlinked wiki covering architecture, pipelines, components, data model, and a sequenced action-point list ready to hand off to an execution tool.
Quick Start
Ask the assistant to use the bleu skill to turn your project idea into a complete end-to-end system blueprint with architecture, components, and action points before writing any code.