bleu

Topics in the source

• Bleu
• Why this skill exists
• Operating principles
• The workspace
• The phased workflow
• Phase 0 - Intake and framing
• Phase 1 - Initial research pass (web + code, if a codebase exists)
• Phase 2 - Vision, architecture, pipelines

Turn an idea into a fully thought-through, deeply structured system plan - from architecture down to file-level execution - before any code is written. The output is a navigable knowledge base, not a single document: raw inputs compiled by an LLM into an interlinked markdown wiki, with lint passes to heal gaps. No RAG, no vector store, no embeddings - the whole plan fits in a modern context window and every claim is traceable to a file a human can open, edit, or delete. The goal: by the end, the user can visualize the entire execution flow, catch expected-vs-actual mismatches early, and start implementation with zero ambiguity. Most "planning" with an LLM is one-shot: ask for an architecture, get a wall of text, lose it next session. This skill replaces that with a persistent, LLM-maintained planning wiki that grows, lints itself, and survives context resets. It's deliberately heavy on structure because the failure mode of light planning is discovering the architectural hole in week three. The strongest single argument for the skill, worth memorizing: The tedious part of maintaining a knowledge base is not the reading or the thinking - it's the bookkeeping. Updating cross-reference

This is an excerpt. Refer to the complete source and its current requirements.