spec-pack-normalizer

To consolidate messy specs into a canonical brief, normalize multi-file inputs like docs, notes, and chat transcripts into a deterministic CANONICAL-BRIEF.md. This process extracts durable facts, constraints, and goals to guide downstream scaffolding.

The best way to extract decisions from scattered planning documents is to normalize them into a batched decision packet. This identifies durable facts, constraints, goals, non-goals, and decisions from multi-source inputs.

Yes, you can normalize chat transcripts and planning notes together into one project spec. The normalization process accepts multi-file inputs across docs, specs, and plans to produce a single deterministic canonical brief.

Yes, the canonical brief structure validates all required sections. It enforces the schema defined in references/brief-schema.md to ensure the generated CANONICAL-BRIEF.md is fully prepared for downstream scaffold agents.

You need to generate a canonical brief when your project inputs are scattered across specs, notes, and chats, making them hard to translate into an actionable overview. It produces a deterministic brief that guides scaffolding.

You should normalize multi-file project inputs before scaffolding to resolve scattered and messy documentation into a clean, actionable format. This ensures downstream scaffold agents receive a validated, deterministic canonical brief.