session-activelisted

The credo behavior for a session running in ACTIVE mode - intensive live collaboration with the user present at the keyboard. Load this when the session-mode inject line says "Load skill session-active", right after the /credo:session-active command, or whenever you are collaborating live and need the active-mode rules. Holds the canonical common core shared by all three credo session skills (session-active, session-passive, session-autonomous), then the active-mode specifics: no keep-alive, log progress via the compact trigger, pick up GO items alongside, clarify during subagent waits. One mode is active at a time.
Marcel-Bich/marcel-bich-claude-marketplace · ★ 13 · AI & Automation · score 80

Install: claude install-skill Marcel-Bich/marcel-bich-claude-marketplace

# session-active - intensive live collaboration A credo session runs in exactly one mode - `active`, `passive`, or `autonomous` - set by the `/credo:session-active|passive|autonomous` commands and surfaced on every prompt by the session-mode inject line. This skill is the umbrella for **active** mode: the user is present and you collaborate intensively and live. It ties the credo building-block skills together for this mode; it does not restate their rules. This file also holds the **canonical common core** that all three session skills share. `session-passive` and `session-autonomous` reference this section instead of repeating it - read it there too. --- # Common core (shared by all three session skills) These rules hold in every mode. The mode-specific sections only add or narrow behavior on top of this core. The core is deliberately thin: most of it points at a credo building-block skill that owns the actual rule, so nothing is duplicated. ## One mode at a time The three modes are exclusive - exactly one is active per session, bound to this session's id and surfaced by the inject line. Switching mode is an explicit user act via the `/credo:session-*` commands (which also couple the keep-alive autonomy flag). Do not assume a mode; read the inject line. ## CLARIFY-FIRST Ask until EVERYTHING is clear. Never assume prematurely that a request is clear. A GO happens only after EXPLICIT user confirmation. - Vague or open requests (for example "implement an obsidian mem