shape-development

Drive a long-running build along one path of an explore-latent DAG, stopping to ask you only the decisions that matter. The skill is the CONDUCTOR: it loads the possibility-graph (whole tree), has you pick a path at gate-0, then fires a headless leg-engine workflow that builds each milestone bounded by its minimum-viable-test — flying all independent legs in parallel waves, parking expensive gates for human batch-resolution, and returning only when nothing can proceed without human input. Use after explore-latent has emitted a validated dag.json. Trigger on 'flight-trajectory', 'fly the path', 'run the build', 'walk the trajectory', 'long-running build', 'drive this build', 'execute the path', 'arm the build job'. Do not trigger for charting the map (use explore-latent), for shaping (use intent-shape), or for a single known edit (just do it).

Externalize the felt-shape of a project — the inviolate gestalt beneath the features — using three sections and two modes, then plant the first primitive (seed) to bridge shape to a concrete artifact. Use upstream of implementation: cold-start when shape isn't articulated, warm when a decision is in front of you. Trigger on 'intent-shape', 'felt-shape', 'parti', 'I am stuck on [project]', 'what is this project actually for', 'shape is not crisp', 'probe me on this'. Do not trigger for implementation, debugging, or feature work.

Chart a validated path through the latent option-space of a bounded project, from here to the target, one cheap-poke at a time. Consumes a matured intent-shape doc. Scout subagents fan out and each propose a whole candidate path; the main loop narrows them against the inviolates and risk-order (validate the core before building the shell); the next step is poked with the cheapest possible artifact, then committed via a handoff file the next session reads cold. Use after intent-shape, when the shape is bounded and the question is 'how do we get there, and what are the forks.' Works greenfield (from a seed) and brownfield (from an existing codebase, consuming intent-shape's gap audit as the frontier). Trigger on 'explore-latent', 'chart the path', 'how do we get there', 'what are the forks', 'sequence this', 'plan the build from the shape', 'find the fun first', 'plan for this existing codebase', 'brownfield plan'. Do not trigger for shaping (use intent-shape), for execution of a single known step, or for debug