Propose

Use Propose when an initialized project needs a new feature, promotion of a Candidate Direction, or a change to future direction. It plans the requested outcome; it does not implement or accept it. For a new engineering review, use Reconcile. For a project without an initialized active or retired status ledger, use Init.

Agent	Request
Claude Code plugin	/memory-bank:memory-bank-propose <requested outcome or candidate direction>
Codex plugin	$memory-bank:memory-bank-propose <requested outcome or candidate direction>
DSH	/memory-bank-propose <requested outcome or candidate direction>

For stage work, add --stages to propose an overview or --stage STG-02 to focus on a specific existing stage. These are request words understood by the skill, not shell options. Naming tabilet/stages.md or a stage ID explicitly in plain English also works. For example:

/memory-bank-propose --stages Divide this project into stages.
/memory-bank-propose --stage STG-02 Develop this idea further.
/memory-bank-propose --stage STG-02 Plan its next milestones.

A later stage may have only a tentative name and brief intent. Developing its context does not schedule milestones. The stage ID remains stable when the name or order changes. An initialized project can adopt stages without restarting Init; Propose places its existing approved horizon in the current stage by default.

Corrective-planning preset

For future execution, --environment dangerous proposes CORRECTIVE_PLANNING: auto; sandbox and least propose confirm. Explicit human policy overrides the preset, and an omitted selector preserves an existing explicit policy. The approved execution request can cover necessary repair planning within its original outcome, grants and limits, including new repair milestones. Propose itself still requires complete proposal approval and never launches execution. See standing corrective planning.

What happens

Propose reads the relevant project memory, code, tests, pending work, candidate directions, and retired IDs. It separates your decisions from observed facts and assumptions. It asks only consequential questions; a clear small addition to a pending milestone goes directly to a concise proposal.

The single approval request names the intended outcome, owner milestones and rows, acceptance and planned verification, priority and dependencies, downstream changes, and exact files to create or edit. An existing pending owner is reused when it fits. A duplicate request creates no second row. Candidate promotion requires a fresh decision about its trigger, dependencies, and acceptance; it is never automatic. Requested features are ordered by approved priority and prerequisites, without engineering defect severity labels.

After approval, Propose checks affected files, worktree changes, and active and retired IDs again. It applies only the approved planning edits. A material change or ID collision calls for a revised proposal. It preserves current row outcomes, counters, local policies, and frozen history. Planned behavior stays in milestone/status records until implementation makes it current fact.

If you want to defer already approved pending work, ask for an explicit stage rescope. Propose shows the exact untouched rows to cancel, their destination stage, and the affected dependencies. Approval changes those rows to [X] with their original identities and withdrawal reason preserved. A future replacement needs fresh planning and a new identity; cancelled work does not prove delivery. Work already underway needs separate handling.

A material change of direction may add an tabilet/evolution/ pair under the project's existing trigger. When goal use is approved, an existing tabilet/memory-bank/suggested.txt launch reference may be refreshed. Neither is automatic for an ordinary feature or candidate promotion.

Propose ends with a planning handoff and explicit verification gaps. Request Next or Goal separately to implement approved work.

For a v1.5.0 project, first migrate the project layout. Then use Upgrade if the project's instructions have not adopted the requested-change procedure. Installing Propose does not change existing project records.