planning

To create an approved phase plan, you research the codebase and institutional learnings, synthesize the findings into a phase-plan.md describing 2-4 phases, and enforce a human approval gate before preparing execution artifacts.

A phase plan is a plain-English document that describes 2-4 meaningful execution phases and enforces a hard approval gate, preventing agents from creating unauditable work by requiring human sign-off before generating current-phase contracts and artifacts.

After phase-plan approval, you prepare the current phase by writing a current-phase contract, generating a story map, and using the br CLI to create normalized beads with verification metadata exclusively for the approved phase.

Yes, you apply the Skill to repositories that include a Pulse CONTEXT.md file to run discovery, map the codebase, retrieve institutional learnings, and write discovery.md and approach.md to close the gap between requirements and implementation.

Yes, the Skill integrates the br CLI to create normalized bead files with verification metadata for the approved phase only, and recommends running bv where available to validate the resulting bead graphs.

Without optional gkg discovery integration, the phase plan still generates discovery.md and approach.md from CONTEXT.md and institutional learnings, but may miss deeper knowledge graph insights during the synthesis of requirements into implementation.