104 lines
2.2 KiB
Markdown
104 lines
2.2 KiB
Markdown
---
|
|
description: Intake an existing TRANSFER.md and build a clean, objective understanding of the current work state. Supports optional arguments to bias focus during intake. No planning or recommendations.
|
|
allowed-tools:
|
|
[
|
|
Bash(cat:*),
|
|
Bash(ls:*),
|
|
Bash(pwd)
|
|
]
|
|
---
|
|
|
|
# /intake — context intake (objective, no planning)
|
|
|
|
You are performing a **context intake** from a previous handoff.
|
|
|
|
Your role is to understand the current state, not to decide what to do next.
|
|
|
|
---
|
|
|
|
## Hard rules (STRICT)
|
|
|
|
- Read and interpret existing information only.
|
|
- Do NOT introduce new goals, plans, or strategies.
|
|
- Do NOT suggest next steps or improvements.
|
|
- Do NOT evaluate the quality of past decisions.
|
|
- Treat all “blockers” as *potential*, not confirmed.
|
|
- If information is missing, state that it is missing — do not infer.
|
|
|
|
---
|
|
|
|
## Optional focus input
|
|
|
|
The user may provide optional arguments after the command.
|
|
|
|
- Treat `$ARGUMENTS` as **intake focus hints only**.
|
|
- Use them to prioritize attention and structure in the summary.
|
|
- Do NOT turn them into tasks or recommendations.
|
|
|
|
User-provided intake focus (if any):
|
|
$ARGUMENTS
|
|
|
|
---
|
|
|
|
## Intake source
|
|
|
|
1) Locate and read `TRANSFER.md` from the project root.
|
|
2) If the file does not exist, clearly state that intake cannot proceed.
|
|
|
|
---
|
|
|
|
## Output requirements
|
|
|
|
- Do NOT modify any files.
|
|
- Do NOT generate plans or TODOs.
|
|
- Produce a **structured intake summary in chat** only.
|
|
|
|
---
|
|
|
|
## Intake summary structure (must follow)
|
|
|
|
### 1. Current Overall Goal
|
|
Restate the goal exactly as documented.
|
|
|
|
---
|
|
|
|
### 2. Current State Snapshot
|
|
Summarize:
|
|
- what is completed
|
|
- what is in progress
|
|
- what is not addressed yet (if stated)
|
|
|
|
---
|
|
|
|
### 3. Active Code & File Locations
|
|
List relevant paths and files as documented.
|
|
|
|
---
|
|
|
|
### 4. Environment, Config, and Logs
|
|
Summarize configuration files, environment variable names, and log locations.
|
|
|
|
---
|
|
|
|
### 5. Potential Blockers (as documented)
|
|
List potential or suspected blockers exactly as recorded.
|
|
|
|
---
|
|
|
|
### 6. Noted Gaps or Unknowns
|
|
Explicitly list:
|
|
- missing information
|
|
- unclear areas
|
|
- references to external systems not fully described
|
|
|
|
(No interpretation, no recommendations.)
|
|
|
|
---
|
|
|
|
## Final step
|
|
|
|
End the response with:
|
|
|
|
> “Context intake complete. Awaiting further instruction.”
|
|
|