Skip to content

Repository navigation

docs: update plan parser PR metadata fields [doc-updater] #2783

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jwbron merged 2 commits into from
May 22, 2026
Merged

docs: update plan parser PR metadata fields [doc-updater] #2783

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
48c081d
docs: update plan parser PR metadata field list
jwbron May 22, 2026
77064a7
docs: clarify context PR fields feed dedicated context PR
egg-reviewer[bot] May 22, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/architecture/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ The plan parser (`shared/egg_contracts/plan_parser.py`) extracts tasks and PR me
2. **YAML front matter** (legacy): A `---`-delimited YAML block at the document start. Supported for backwards compatibility.
3. **Markdown regex** (fallback): Parses `[TASK-X-Y]` patterns from markdown. Fragile and may miss tasks if LLM output format drifts.

The parser also extracts optional PR metadata (title and description) from the `pr:` field in the YAML data. If provided, this metadata is used when creating the pull request during the implement phase.
The parser also extracts optional PR metadata (`title`, `description`, `test_plan`, `manual_steps`, `context_title`, `context_description`) from the `pr:` field in the YAML data. If provided, this metadata is used when creating the pull request during the implement phase.

**Role-aware task assignment**: Tasks can include an optional `role` field (`coder`, `tester`, or `documenter`) that assigns the task to a specific execution agent. The parser propagates this field through `ParsedTask` into the contract `Task` model. During the implement phase, `_build_role_context()` filters tasks by role so each agent only sees its assigned work. See [Agent Roles Reference](../reference/agent-roles.md#role-aware-task-assignment) for details.

Expand Down
Loading