activity-recap
FreeUse when the user needs a standup-ready summary of recent project activity from local evidence.
The English summary is being prepared. Showing the original description.
Use when uncertainty remains and the minimum useful sequence of questions should be asked.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Lifecycle stage: INTAKE
Use when missing answers block product, design, or engineering decisions.
Do not use when this trigger is absent; choose the command or skill that owns the requested state, artifact, and verification gate.
| Shortcut | Rebuttal |
|---|---|
| "This is obvious." | Write the assumption and evidence. If you cannot, it is not obvious. |
| "We can do this later." | If the missing step changes the decision, do it now or state the risk. |
| "The user wants speed." | Reduce scope; do not skip the quality bar. |
| "This does not need verification." | Every important claim or behavior needs proof. |
Open Questions plus assumptions
The artifact should be concise, auditable, and include evidence, blockers, and next action so another agent can resume.
Trigger: uncertainty remains after retrievable evidence has been checked. Action: ask the smallest useful next question or choose the safest documented default in noninteractive mode. Output artifact: intake or grill artifact with blockers and next action. Verification: cite evidence checked, why the question changes action, and stop condition if no answer is available.
A plan is blocked by "needs approval." The ladder should ask the smallest next question first: what side effect is approval-gated, what safe read-only alternative exists, what assumption can unblock planning, and what evidence would change the route.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when the user needs a standup-ready summary of recent project activity from local evidence.
The English summary is being prepared. Showing the original description.
Use when a command, adapter, or runtime smoke depends on proving an agent runtime's capabilities before trusting command routing, writes, shell access, or validation claims.
The English summary is being prepared. Showing the original description.
Use when agent-produced work needs a safety, evidence, and reliability check before handoff, merge, or trust.
The English summary is being prepared. Showing the original description.
Use when an output artifact, template, schema, example, or handoff field must stay aligned across commands, skills, docs, and validators.
The English summary is being prepared. Showing the original description.
Agent Brain /brain-brief: after intake, research, and grill have enough signal.
The English summary is being prepared. Showing the original description.
Agent Brain /brain-build: an implementation plan has a selected task and validation method.
The English summary is being prepared. Showing the original description.