Skip to content

docs: define plan status contract#1602

Open
YOMXXX wants to merge 2 commits into
obra:devfrom
YOMXXX:docs/plan-status-contract
Open

docs: define plan status contract#1602
YOMXXX wants to merge 2 commits into
obra:devfrom
YOMXXX:docs/plan-status-contract

Conversation

@YOMXXX
Copy link
Copy Markdown

@YOMXXX YOMXXX commented May 22, 2026

Summary

  • Add docs/plan-status.md with a lightweight markdown contract for plan task status.
  • Define status derivation from task headings, checkbox steps, optional Status / Evidence / Next metadata, and conflict handling.
  • Document context-frugal resume behavior without adding a new slash command or separate state store.
  • Link the contract from the README and writing-plans skill.
  • Connect executing-plans and subagent-driven-development to the contract so they scan existing status, resume from the right task, and update plan state when possible.

Why

Refs #1599, #1075, #931, and #1597.

This keeps the user-facing model as ordinary conversation instead of adding a new slash command. The first PR stays docs/skill-instructions only: it gives reviewers a narrow contract and execution workflow to validate before any follow-up runtime or eval harness work.

Verification

  • git diff --check
  • git diff --cached --check
  • test -f docs/plan-status.md
  • rg -ni "plan status contract|docs/plan-status.md|\.\./\.\./docs/plan-status.md|blocked|skipped" README.md skills/writing-plans/SKILL.md docs/plan-status.md
  • rg -n "plan status contract|blocked.*resolved|remaining tasks|Do not make subagents read|current status" skills/executing-plans/SKILL.md skills/subagent-driven-development/SKILL.md docs/plan-status.md README.md

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant