From session-orchestrator
Starts a development session (housekeeping, feature, or deep), autonomously researches full project state, and presents structured findings with recommendations.
npx claudepluginhub kanevry/session-orchestrator --plugin session-orchestratorhousekeeping|feature|deep# Session Start You are beginning a new development session. The user has invoked `/session` with type: **$ARGUMENTS** (if empty, auto-detect from the project's `## Session Config` block or default to `feature`). **Argument validation:** Valid session types are `housekeeping`, `feature`, and `deep`. If `$ARGUMENTS` is not empty and does not match any valid type, inform the user: "Invalid session type '$ARGUMENTS'. Valid types: housekeeping, feature, deep." Then auto-detect from the project's `## Session Config` block or default to `feature`. **Your job: Autonomously research the full pro...
/sessionSaves, resumes, and lists development sessions across conversations, preserving context, decisions, progress, and key files in .claude/sessions/.
/sessionDisplays the current Claude session ID by outputting the value of the `${CLAUDE_SESSION_ID}` variable.
/sessionSaves current planning session to structured Markdown file in sessions/planning/ with date-topic filename. Supports custom description and --draft/--finalized flags.
/sessionDisplays the current Claude session ID by outputting the value of the `${CLAUDE_SESSION_ID}` variable.
You are beginning a new development session. The user has invoked /session with type: $ARGUMENTS (if empty, auto-detect from the project's ## Session Config block or default to feature).
Argument validation: Valid session types are housekeeping, feature, and deep. If $ARGUMENTS is not empty and does not match any valid type, inform the user: "Invalid session type '$ARGUMENTS'. Valid types: housekeeping, feature, deep." Then auto-detect from the project's ## Session Config block or default to feature.
Your job: Autonomously research the full project state, then present structured findings with recommendations for the user to approve before creating a wave plan.
Invoke the session-start skill. Follow its instructions precisely. Do NOT skip any phase. Do NOT make assumptions — verify everything in code and on the VCS platform.