← ClaudeAtlas

role-planlisted

Assign this session the credo plan/clarify role - the default owner of clarifying items in 1_clarify/, WITHOUT commits or push (the task/build role owns commits and push). Use ONLY when the user actually assigns this role to you, for example "you are (now) the plan/clarify agent", "you clarify the items", "take over the clarifying / the clarify items", "act as the plan agent", "switch into the plan/clarify role", "du bist (jetzt) der plan/clarify agent", "übernimm das Klären / die clarify-items", "wechsel in die plan/clarify rolle" - or when the /credo:role-plan command is run. Do NOT use for general talk ABOUT roles, explanations, or questions like "what does the plan agent do". It writes a persistent, compact-safe per-session marker (re-injected every turn) so the role survives compaction.
Marcel-Bich/marcel-bich-claude-marketplace · ★ 13 · AI & Automation · score 80
Install: claude install-skill Marcel-Bich/marcel-bich-claude-marketplace
# Session Role: plan / clarify Set this session's credo ROLE to **plan / clarify**. This is a guiding default owner of clarifying items in `1_clarify/`, WITHOUT commits or push. Committing and pushing are the task/build role's job, so a single index owner avoids a race on `.git/index.lock`. A role is orthogonal to the session mode (active | passive | autonomous): it can coexist with any mode. It is a guiding default, NOT a fixed constraint - on the user's wish you may still do mixed work, and an explicit user instruction always overrides the role. ## When to use - The user runs `/credo:role-plan` (the explicit, deterministic, guaranteed path). - The user assigns you this role in passing (best-effort, casual path) - for example "you are now the plan/clarify agent", "you clarify the items", "take over the clarifying", "act as the plan agent", "uebernimm das Klaeren", "du bist der plan/clarify agent". Do NOT trigger on general discussion about roles, on explanations, or on questions such as "what does the plan agent do" - those are not an assignment. ## What it does Write the persistent, per-session role marker. It is keyed by session_id under the session-roles dir and re-injected on every prompt by `role-inject.sh`, so it survives context compaction, new sessions and subagents (stored on disk, not in context): ```bash "${CLAUDE_PLUGIN_ROOT}/hooks/role-set.sh" plan ``` ## Sandbox pre-work For WRITING clarify pre-work that needs no product decision but evidence - a