메뉴
Use when you need to delete specific outdated or incorrect memories.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | team-shinchan:forget |
| description | Use when you need to delete specific outdated or incorrect memories. |
| user-invocable | false |
Remove outdated or incorrect learnings from memory.
/team-shinchan:forget # Interactive mode
/team-shinchan:forget "Redux" # Remove learnings containing "Redux"
/team-shinchan:forget --all # Clear all learnings (with confirmation)
/forget)🗑️ [Forget] Current learnings:
1. [preference] Use Zustand over Redux
2. [pattern] Early returns for validation
3. [convention] Use pnpm, not npm
4. [mistake] Always null-check before .map()
Which learning to remove? (Enter number or keyword)
/forget "Redux")🗑️ [Forget] Searching for: "Redux"
Found 1 matching learning:
• [preference] Use Zustand over Redux
Remove this learning? (y/n)
If confirmed:
✅ Removed: "Use Zustand over Redux"
📁 Updated: .shinchan-docs/learnings.md
/forget --all)⚠️ [Forget] WARNING: This will delete ALL learnings!
Current count: 15 learnings
Are you sure? Type "DELETE ALL" to confirm:
If confirmed:
✅ Cleared all learnings.
📁 Reset: .shinchan-docs/learnings.md
💡 Start fresh with /team-shinchan:learn or just work!
| Situation | Action |
|---|---|
| Learning is outdated | /forget "old pattern" |
| Learning was wrong | /forget "incorrect thing" |
| Project changed direction | /forget --all (careful!) |
| Too many irrelevant learnings | Selective /forget |
--allUse when you have a large-scale, multi-phase project requiring orchestrated execution.
Use when you need persistent looping until a task is fully complete.
Deterministic adversarial code review for high-stakes scope — independent per-dimension review, a non-skippable per-finding refutation, completeness + interaction critics, and a deterministic 3-lens rubric judge panel. Opt-in main-loop Workflow tier.
Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.
Deterministic competitive code tournament — N builders independently solve one task and return patches, an Action-Kamen judge scores them head-to-head, the winner is picked by score and applied. Opt-in main-loop Workflow tier.
Deterministic adversarial debate for high-stakes or irreversible decisions — mandatory refutation plus a scored judge panel. Opt-in main-loop Workflow tier.