القائمة
Cancel a research plan. Updates status to CANCELLED and moves to archive/. Use when research is no longer needed or has been superseded.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | research-cancel |
| description | Cancel a research plan. Updates status to CANCELLED and moves to archive/. Use when research is no longer needed or has been superseded. |
Cancel a research plan that is no longer being pursued.
Identify the research to cancel:
Ask for cancellation reason (optional but recommended):
Update research files:
Update research-plan.md status header:
## Status: CANCELLED
**Cancelled:** YYYY-MM-DD
**Reason:** [User's reason, if provided]
**Superseded by:** [Reference, if applicable]
Update .research-state.json:
{
"status": "cancelled",
"cancelled_at": "2026-01-28T10:30:00Z",
"updated_at": "2026-01-28T10:30:00Z",
"cancellation_reason": "No longer needed",
"superseded_by": null,
...existing fields...
}
Move to archive:
mv .gumbo/research/NNNN-topic-name .gumbo/research/archive/
Confirm to user:
**Cancelled:** `.gumbo/research/archive/NNNN-topic-name/`
**Status:** CANCELLED
**Reason:** [reason]
**Questions answered:** X/Y at time of cancellation
Draft or amend an Architecture Decision Record (ADR) from a research synthesis or a design decision. Use when a decision needs to become a durable, reviewable record — and when extending or correcting a decision that has already landed.
Review an Architecture Decision Record (or coupled ADR set + cover) for grounding, decisiveness, completeness, and internal consistency before it is approved or landed — and to catch the drift that iteration introduces across coupled drafts and the cover. Reports findings; does not auto-fix unless asked.
Create and maintain a roadmap that sequences milestones and the plans, research, and decisions that fulfill them. Use when work spans many artifacts over time and needs one living place that shows the sequence, status, dependencies, and risks.
Create implementation plans following project conventions. Use when planning new features, refactors, or significant changes.
Resume working on an in-progress implementation plan. Finds incomplete plans and provides context to continue.
Review an implementation plan for correctness, feasibility, completeness, and internal consistency before it is approved or implemented — and to catch the reference drift that iteration introduces. Reports findings; does not auto-fix unless asked.