Build the delivery plan

Scene 1 of 15 — Continue into specification planning

At the approved idea checkpoint, /plan automatically loads develop-obsidian-spec.

Internal skill step · no new user command

SoherAgentThe approved idea is durable. Proposed /plan is continuing into specification planning; no execution authority is created.

/planLoad develop-obsidian-spec internallyautomatic

checkpointApproved idea and provenanceverified

executionNo handoff, lease, or workernone

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 2 of 15 — Discover the approved idea

Find exactly one eligible approved idea before opening bounded context.

Automatic when unique · ask only if ambiguous

discoverEligible approved ideas1 found

matchService Contract Intelligence MVP · exact initiative identityunique

openBounded idea + initiative context onlyselected

authoritySelection does not authorize implementationnone

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 3 of 15 — Verify provenance

Verify identity, approval, and provenance before drafting.

Fail closed on ambiguous provenance

approvalIdea decision = approvedverified

identityInitiative and source IDs matchverified

provenanceBrief → initiative → approved ideaexact

authorityNo handoff, lease, or workernone

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 4 of 15 — Draft the specification

Draft testable behavior and recovery boundaries.

Proposed specification

Service Contract Intelligence MVP specification

P1Import one synthetic contract; cite supported obligations and dates; flag weak evidence as Needs reviewproduct

P2Grounded answers cite a passage or clearly say the answer was not foundproduct

H1A human records Confirmed or Needs review for each resultreview

T1Fixture-based extraction, citation, answer, and review-state teststest

R1Disable AI extraction cleanly; keep the source and review record intactrecovery

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 5 of 15 — Approve the specification

Make the required specification disposition.

Focused mandatory decision

ask_userv0.12.0

Question / context
What is the final specification disposition?

⌕ Filter options

>Approve specificationAllow reviewed ticket planning

ReviseReturn to structure and boundaries

HoldKeep draft without advancing

DeclineRecord a stop decision

Option previewApprove the system, test, recovery, and non-goal boundaries. No implementation authority is created.

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 6 of 15 — Save the specification

Save and verify the approved specification checkpoint.

Parent-owned sequential planning mutations

writeApproved specification checkpointsaved

link checkApproved idea → approved specificationverified

reopenSpecification status and provenanceverified

executionNo handoff or implementationfalse

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 7 of 15 — Open the detailed specification in Obsidian

The canonical specification opens at the top with architecture, fourteen sections, traceability, and visible scroll continuation.

Detailed sanitized Obsidian recreation · ticket planning not started

Detailed sanitized Obsidian reading view of the approved Service Contract Intelligence MVP specification, showing metadata, architecture, user stories, requirements, data contracts, security, recovery, tests, delivery structure, decisions, traceability, and checkpoint. — **Generated artifact:** a scrollable canonical specification with fourteen detailed sections, testable requirements, traceability, and recovery boundaries.Implementation authority: false

Build the delivery plan · 07/15 · approved specification opened · ticket planning next

SANITIZED RECREATION · NO HANDOFF OR EXECUTION

Scene 8 of 15 — Continue into ticket planning

After specification approval, /plan automatically loads develop-obsidian-tickets.

Internal skill step · no new user command

SoherAgentThe specification is approved and verified. Proposed /plan is continuing into ticket planning automatically.

/planLoad develop-obsidian-tickets internallyautomatic

checkpointApproved specification and provenanceverified

executionNo handoff or implementationfalse

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 9 of 15 — Discover the specification

Find exactly one eligible approved specification and verify its chain.

Automatic when unique · exact provenance

discoverEligible approved specifications1 found

matchService Contract Intelligence MVP · exact idea provenanceunique

verifyApproval, source links, non-goals, recoveryexact

authorityNo handoff or implementationnone

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 10 of 15 — Draft the ticket graph

Draft the dependency graph, frontier, and parent-owned gates.

V1-S2 waits for reviewed V1-S1 completion

Ticket graph

T01Cited contract extractionfrontier

T02Grounded summary + human reviewsame V1-S1 batch

S2Engineering adoption kitblocked

Integration · parent validates sequentially

Review · standards + specification passes

Handoff · not created by ticket planning

Execution · false

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 11 of 15 — Confirm graph and gates

Confirm ticket granularity and dependencies.

Focused mandatory decision

ask_userv0.12.0

Question / context
Is the proposed granularity and dependency graph correct?

⌕ Filter options

>Keep V1-S1 as T01 → T02One ready batch; sequential parent gate

Split into later batchesRequire another graph review

Return to specificationRevise scope first

Option previewKeep exact eligible batch V1-S1. V1-S2 remains blocked until all V1-S1 work passes.

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 12 of 15 — Approve the ticket bundle

Make the required ticket-plan disposition.

Focused mandatory decision

ask_userv0.12.0

Question / context
What is the final ticket-plan decision?

⌕ Filter options

>Approve ticket bundleAllow final initiative routing

Revise bundleReturn to graph decisions

HoldKeep tickets without routing

DeclineRecord a stop decision

Option previewApprove the reviewed graph and parent-owned gates as planning artifacts only.

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 13 of 15 — Choose the final route

Choose the final initiative route from the seven current options.

Focused mandatory final-route decision

ask_userv0.12.0

Question / context
How should this approved planning bundle proceed?

⌕ Filter options

Create and activate a new projectRoute and activate the minimum workspace

Propose a new project without activationRecord an incomplete resumable proposal only

Attach to an existing projectVerify one exact project first

>Keep as approved standalone workFinish planning without handoff or execution

Attach to a cross-project programVerify one exact program first

Defer the initiativePreserve trigger, dependency, and date

Reject the initiativePreserve rationale and reconsideration condition

Option previewSelected: Keep as approved standalone work. Ticket planning records the route but creates no handoff or execution authority.

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 14 of 15 — Write route and links

Write the route and links in strict sequence.

Parent-owned approval-gated Obsidian writes

write 1Approved ticket bundlesaved

link 1Specification → ticket bundleverified

write 2Final route: approved standalone worksaved

link 2Initiative → final routeverified

Build the delivery plan · proposed /plan concept · no execution authority

concept recreation · not implemented runtime

Scene 15 of 15 — Complete autonomous planning

Proposed /plan has orchestrated idea, specification, and ticket planning to a durable stop.

No automatic handoff or execution

SoherAgentProposed /plan complete. Initiative, approved idea, approved specification, reviewed ticket bundle, standalone route, and graph are durable.

User commands so far · /plan on

Next user command · /yolo on

Eligible batch · V1-S1 only

Implementation · false

›

Build the delivery plan · /plan concept complete · next user command /yolo on · implementation false

concept recreation · not implemented runtime