Collect Task Context
Gather the smallest reproducible context packet for one task.
This is not a repo dump. Include only evidence that helps plan, edit, or verify the task.
Process
- Identify the task, expected behavior, and acceptance criteria.
- Read project agent docs and relevant domain docs.
- Map allowed changes, read-only context, and forbidden paths.
- Find change candidates, call sites, interfaces, tests, fixtures, and configs.
- Record verification commands and known gaps.
- Capture provenance: branch, base, date, and commands used.
Use packet-format.md when writing a formal packet.
Include
- task summary
- relevant files and symbols with why each matters
- scope and forbidden changes
- product/domain rules
- architecture, API, DB, or event contracts when relevant
- focused tests and broader checks
- assumptions and open questions
Exclude
- generated files unless directly relevant
- vendor and caches
- broad docs with no task-specific takeaway
- secrets, tokens, private credentials
- stale docs unless conflict matters
Output
Return ready, ready_with_assumptions, or not_ready.
If not ready, name the blocking missing fact. If ready, keep the packet compact enough that another agent can use it immediately.
1---2name: collect-task-context3description: Builds a minimal task-specific context packet for an agent. Use when user wants context for a coding task, needs to prepare an agent handoff, or asks what files, constraints, tests, and evidence should be given to an implementation agent.4---56# Collect Task Context78Gather the smallest reproducible context packet for one task.910This is not a repo dump. Include only evidence that helps plan, edit, or verify the task.1112## Process13141. Identify the task, expected behavior, and acceptance criteria.152. Read project agent docs and relevant domain docs.163. Map allowed changes, read-only context, and forbidden paths.174. Find change candidates, call sites, interfaces, tests, fixtures, and configs.185. Record verification commands and known gaps.196. Capture provenance: branch, base, date, and commands used.2021Use [packet-format.md](references/packet-format.md) when writing a formal packet.2223## Include2425- task summary26- relevant files and symbols with why each matters27- scope and forbidden changes28- product/domain rules29- architecture, API, DB, or event contracts when relevant30- focused tests and broader checks31- assumptions and open questions3233## Exclude3435- generated files unless directly relevant36- vendor and caches37- broad docs with no task-specific takeaway38- secrets, tokens, private credentials39- stale docs unless conflict matters4041## Output4243Return `ready`, `ready_with_assumptions`, or `not_ready`.4445If not ready, name the blocking missing fact. If ready, keep the packet compact enough that another agent can use it immediately.46
mergemat