rore

Use when showing or updating roadmap state in a repo with the minimap roadmap convention (board.md, scope.md, features/, ideas/). Not for arbitrary spec review.

Use when setting up agent governance for a repo, or when working in a repo that contains agent-policy.yaml. Classifies structural risk and routes human attention to red-zone changes.

Use when you need to explicitly search, store, or debug Pallium memory beyond what automatic injection provides. Triggers on: "remember this", "why don't you remember", "what do you know about", memory debugging, or when injected context is insufficient.

Use when tasks need 3+ steps, involve architecture/refactor seams, behavior-parity risk, or bug/test/CI failures. Skip for trivial one-liners, pure Q&A, or when the user explicitly asks to skip planning.

Review and shape Pallium features, plans, implementations, and cross-thread work for product alignment, architectural fit, safety, and proportional design. Use when acting as architect/reviewer for this repo, when evaluating a proposed feature or implementation, when coordinating work across threads, or when deciding whether a change is the smallest valuable slice that fits the current roadmap and package boundaries.

Use when reading, updating, or reorganizing roadmap state in a repo that uses the minimap file convention. Apply for roadmap planning and status changes; do not use for general engineering workflow unless the task is specifically about roadmap files.

Repo-adapted execution workflow for non-trivial bear-cli tasks. Trigger for tasks with 3+ steps, architectural decisions, bug investigations, or when user asks for plan-first or verification-heavy execution. Skip for trivial one-step edits or pure Q&A.

Use when setting up agent governance for a repo, or when working in a repo that contains agent-policy.yaml. Classifies structural risk and routes human attention to red-zone changes.