Slash Command

/init-workspace-flow-shells

Generates shell config files from KB schemas for IDE/CodingAgent to load context and invoke skills. Phase 2 of init-workspace-flow; skips in plugin mode and updates state.

developer-tools

automation

npx claudepluginhub griddynamics/rosetta --plugin core

Prompt Preview

<init_workspace_flow_shells>

<description_and_purpose>
Generates shell config files so subsequent sessions can load context and invoke skills. Proof: shell configs exist on disk and state reflects creation status.
</description_and_purpose>

<workflow_context>
- Phase 2 of 8 in init-workspace-flow
- Input: state.mode, state.plugin_active
- Output: shell configs, bootstrap rule, load-context shell
- Prerequisite: Phase 1 complete, state.mode set
</workflow_context>

<phase_steps>
1. Check mode, skip if plugin
2. ACQUIRE and execute shell generation skill
3. Update state with shell status
</...

Command Content

Other plugins with /init-workspace-flow-shells

/kasi-init

Initializes Kasidit: prompts for default mode, runs installer to copy hooks/seed Gravity hub, wires Claude settings for out-of-box sessions.

kasidit

/install-context

4.0k

Installs OpenAgents Control context files for the project using the context-setup skill. Supports --profile=<profile>, --force, --dry-run flags.

oac

/flow-init

Installs or updates Flow framework by downloading 29 slash commands, 8 agent skills, 1 agent, docs, and examples from GitHub repo. Detects mode, prompts for confirmation.

flow

/setup

Initializes Claude Code projects in Plugin or Clone mode, configures hooks globally or per-project, creates settings files/directories and cleans old configs. Supports --hooks, --global, --project, --verify flags.

7 tools

cc-best

Stats

Parent Repo Stars15

Parent Repo Forks6

Last CommitMar 25, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

<init_workspace_flow_shells> <description_and_purpose> Generates shell config files so subsequent sessions can load context and invoke skills. Proof: shell configs exist on disk and state reflects creation status. </description_and_purpose> <workflow_context> - Phase 2 of 8 in init-workspace-flow - Input: state.mode, state.plugin_active - Output: shell configs, bootstrap rule, load-context shell - Prerequisite: Phase 1 complete, state.mode set </workflow_context> <phase_steps> 1. Check mode, skip if plugin 2. ACQUIRE and execute shell generation skill 3. Update state with shell status </...

<init_workspace_flow_shells>

<description_and_purpose> Generates shell config files so subsequent sessions can load context and invoke skills. Proof: shell configs exist on disk and state reflects creation status. </description_and_purpose>

<workflow_context>

Phase 2 of 8 in init-workspace-flow
Input: state.mode, state.plugin_active
Output: shell configs, bootstrap rule, load-context shell
Prerequisite: Phase 1 complete, state.mode set </workflow_context>

<phase_steps>

Check mode, skip if plugin
ACQUIRE and execute shell generation skill
Update state with shell status </phase_steps>

<check_mode step="2.1">

Read agents/init-workspace-flow-state.md
If state.plugin_active == true: mark Phase 2 skipped, proceed to Phase 3
If upgrade mode: check which shells already exist </check_mode>

<execute_shells step="2.2">

ACQUIRE init-workspace-shells/SKILL.md FROM KB
Execute shell generation per skill logic
In upgrade mode: create missing shells only, preserve existing </execute_shells>

<update_state step="2.3">

Write to agents/init-workspace-flow-state.md:
- Shell configs status (created | updated | skipped)
- Bootstrap rule status
- Phase 2 completion timestamp
Log gaps for Phase 7 </update_state>

<validation_checklist>

Plugin mode: phase marked skipped, no shell files modified
Install mode: all expected shell files exist on disk
Upgrade mode: only missing shells created, existing preserved
Bootstrap rule file exists with ACQUIRE instruction for load-context </validation_checklist>

</init_workspace_flow_shells>