What problem does it solve? Planning artifacts in an AI-driven change pipeline tend to grow without bound, duplicating information and inflating review cost. This Skill establishes a single normative contract that fixes what each artifact owns, what it must not contain, and its word budget, so every writer and reader in the ptp pipeline works from the same rules. ## Core Features & Use Cases - Ownership table with budgets: Assigns each artifact (brainstorm.md, proposal.md, spec deltas, design.md, tasks.md, effort.md, prd.md, analysis.md) an exclusive scope and a hard or soft word budget backed by config keys. - Shape and policy rules: Enforces one-line effort.md, conditional design.md, build-state declarations in proposals, full MODIFIED delta reproduction, and a current-state-only update policy with no history sections. - Contract versioning: Distinguishes ptp-compact changes from legacy spec-driven changes via .openspec.yaml so old changes are interpreted under their original rules. - Use Case: A planner drafting a change that cannot fit the 400-word proposal budget returns NEEDS SPLIT instead of silently exceeding the limit, keeping review effort bounded. ## Quick Start Ask the AI to check whether the proposal.md and tasks.md in the current openspec change comply with the ptp compact artifact contract.
