woostack-prepare

woostack-prepare

woostack-prepare is the thin planning-only composition for feature and defect requests. It ends with one verified GitHub specification parent, PR-sized native children, their real prerequisite edges, and a complete planning handback. The handback can be passed to Orchestrate as work context; Orchestrate may also interpret other understandable tracker content. Prepare never edits implementation source, creates a source branch or worktree, commits, opens a pull request, dispatches workers, or invokes Execute or Orchestrate.

Prepare reports Plan's native publication state truthfully. If another authorized chat route creates the complete issues and readable index but cannot install native relationships, those issues remain declared Orchestrate input after independent reads; they are not a successful native Plan result.

Command

/woostack-prepare <goal-or-defect> [--parent-issue new|<exact canonical GitHub parent URL>]

The optional selector is passed unchanged to public woostack-plan. new requests one new specification parent; an existing selector must be one exact canonical GitHub issue URL. Conflicting, repeated, malformed, foreign, or missing publication scope blocks before Plan publication. For an explicit GitHub Project, invoke Plan directly with its exact selector; Prepare does not invent a second destination or configuration. This selector configures Plan's publication destination, not Orchestrate's later admission.

Prepare has no --run, --project, remote-sync selector, compatibility alias, or local planning ledger. It does not discover or mutate .woostack/tmp/runs/; retained historical runs remain readable and are never migrated or rewritten. A prior run or issue is usable only when the caller supplies its complete content and exact identity for fresh phase validation.

Ownership and phase selection

Prepare owns only the overall goal classification, phase ordering, unresolved user decisions, and the terminal handoff. The public phases own their own contracts:

• Feature. For a goal or incomplete specification, pass a complete plain packet to public woostack-ideate. Ideate asks only for missing user-owned decisions and returns the complete verified specification. If a complete specification or Ideate handback is already supplied, reuse its settled decisions and start at Harden.
• Defect. Invoke read-only woostack-debug first, or independently revalidate a supplied complete diagnosis packet. Carry observed and expected behavior, the causal chain, exact source/runtime/reproduction evidence, smallest complete correction, affected and unaffected surfaces, risks, and regression/smoke checks into the specification. A symptom, alert, issue body, PR description, or plausible theory is not proof. Missing, stale, contradictory, or non-reproducible causal evidence stops at a diagnosis blocker; Prepare never guesses a correction.
• Harden. Pass the complete specification and exact repository/evidence identity to public woostack-harden. Harden reconciles repository facts and candidate issue contracts, preserves approved decisions, and asks before material corrections. Prepare does not clone Harden's procedure or silently accept its recommendations.
• Plan. Pass Harden's complete handback, the approved specification, exact repository/baseline and evidence identity, and the selected parent scope to public woostack-plan. Plan is the sole publisher: it decomposes the smallest coherent PR-sized graph, writes/reuses the GitHub parent and children, creates only the declared native prerequisite edges, and independently reads every result back.

A complete input may start at the relevant phase. An approved specification or existing parent does not cause Ideate to repeat settled questions; a fresh complete diagnosis does not cause Debug to repeat unchanged proof. Revalidate only stale, conflicting, or newly exposed evidence. Prepare never adds an approval gate merely because a phase is composed. User approval of material decisions belongs to Ideate and the explicit correction dialogue; Plan publishes only a complete handback with no unresolved decisions or discrepancies.

Input contract

Every phase packet uses the shared plain planning input and handback contract:

• exact canonical repository, admitted immutable baseline, and checkout identity when inspection is requested;
• every evidence identity and scoped observation, using immutable Git data, exact canonical issue or PR URLs, or captured runtime/command evidence;
• complete content, including goal, users, behavior, constraints, exclusions, architecture choices, acceptance, verification expectations, risks, and removal/reuse decisions; and
• an empty unresolved-question section before publication.

Defect packets additionally preserve the complete Debug handback. Candidate issue plans retain stable task IDs, positive ordinals, bounded scope, non-goals, affected interfaces, observable acceptance, verified check definitions and one real smoke scenario, risks, exact prerequisites, and Git-parent selection policy. If the work changes storage or an API, retain the user-verified ## Data models section; otherwise omit it. Repository conventions and agent recommendations are evidence, never user decisions.

Publication and recovery boundary

Prepare does not write GitHub issues. Plan owns one publication and its recovery evidence. A successful result reports:

1. the exact verified specification-parent URL;

2. display-ordered child URLs and stable task identities;

3. the normalized native technical prerequisite graph, without treating ordinals as edges;

4. the repository/baseline and evidence identities used for the read-back; and

5. the complete planning handback and, when available, this separate convenience action:

   /woostack-orchestrate --issue <verified specification-parent-URL>
   

The command is a handoff hint, not an exhaustive Orchestrate input form. The user may instead provide the complete handback or understandable tracker content in conversation. A successful Plan publication is the native parent/child graph plus a complete read-back of its declared native prerequisite edges; independently verified tracker content whose native relationships are absent or incomplete remains usable declared context, and Prepare never claims those relationships exist. woostack-orchestrate owns every later step.

A parent-only result, missing child/contract, ambiguous membership, unknown dependency meaning, partial pagination of a required successful read, unknown mutation outcome, or incomplete Plan read-back is not a complete Plan publication. Preserve every confirmed URL/ID and resume Plan at its first unproved relationship or read-back boundary; never replay a create, allocate a replacement, or call partial Plan publication a harmless mirror warning. The exact existing parent and child IDs are the recovery identity.

Hard boundaries

• Planning only: no implementation source edits, generated app files, source branches/worktrees, commits, pushes, pull requests, review actions, Execute workers, Orchestrate workers, or merges.
• Debug returns read-only diagnosis; its handback is evidence, not approval or execution authority.
• Ideate and Harden remain directly callable and exchange complete plain packets. Plan remains directly callable and is the only issue publisher. Prepare composes them one-way and never calls itself recursively or creates a hidden manifest or mirror.
• GitHub issue publication and native relationship read-back must be complete. A mandatory Project or replacement local work board is not a gate.
• Existing user runs, issue records, remote Projects, and historical reports survive unchanged. Retained retired-wrapper drafts can be supplied explicitly after identity and freshness validation; there is no automatic conversion, old-command alias, or remote publication of a local draft.
• Agents never mark a PR ready, enable auto-merge, enqueue, merge, force-push, or claim delivery, passing checks, review, product acceptance, or merge from issue lifecycle alone.

When Prepare is invoked with a small fix, an explicit word such as “fix”, “build”, or “complete”, or an already-approved one-PR request, it still stops at a verified parent plus executable child issue. Direct implementation remains an explicitly selected bounded woostack-execute request. If a user wants only diagnosis, use Debug directly; if they already have approved content, use Harden or Plan directly. Prepare prints the Orchestrate command only as a suggestion.