pm-long-horizon-planning

PM Long-Horizon Planning

Non-negotiable outcome

Compile the source taskbook as governed input. Do not treat it as infallible prose. Produce exactly one current Product Brief, or stop with needs_admin_decision when a blocking source or feasibility finding exists.

Auto-injection is recommendation only. It is never evidence that this skill was executed.

Required resources

Read these files completely at the named phase:

• Before building the IR, read references/planning-model-contract.md and references/taskbook-audit-findings.md.
• Before rendering the artifact, read references/product-brief-contract.md and assets/long-horizon-product-brief-template.md.
• Before submitting or acting on a decision, read references/planning-gate-contract.md.

Workflow

0. Bind identity and target

1. Confirm the caller is PM and is in an active Runtime session.
2. Resolve one root task_id, non-empty thread_key, and canonical Brief path.
3. Accept a child rework only when parent, planning_target_task_id, thread, and an ADMIN/Planning-Gate rework authorization all bind it to the root.
4. Reject only the invalid operation when binding fails. Do not terminate the Session or Task.
5. Do not write a root Brief from CHAT-* with an empty thread.

1. Ingest the complete taskbook

1. Read from the first byte through EOF, in chunks when necessary.
2. Record absolute source identity, version, SHA-256, byte/line counts, read time, ranges read, reference set, and read_complete=true only after EOF.
3. Resolve file paths, URLs, commits, ports, versions, task IDs, and named authorities.
4. Check references read-only. Do not draft a summary Brief before ingestion completes.

2. Audit before planning

1. Classify each substantive statement as normative_constraint, target_design, current_fact, estimate, assumption, reference, or authority_boundary.
2. Assign stable REQ-0001 IDs with source lines and modality.
3. Audit structure, contradictions, references, fact drift, authority, feasibility, roles/acceptance, recovery, reproducibility, and state vocabulary in that order.
4. Record findings using the finding contract. Distinguish blocking, warning, and info.
5. For infeasibility, show a minimal conflicting requirement set and candidate resolutions. Never choose which requirement becomes void.
6. Normalize editorial errors only when scope, role, budget, date, gate, acceptance, and authority stay unchanged.
7. On any blocking finding, set artifact status to needs_admin_decision, report the finding, and stop for ADMIN. Do not silently repair intent.