Slash Command

/init-workspace-flow-questions

Prompts user with reflective questions to resolve gaps from prior workspace analysis phases, maps answers to files, spawns subagents for updates, and verifies resolutions.

developer-tools

npx claudepluginhub griddynamics/rosetta --plugin core

Prompt Preview

<init_workspace_flow_questions>

<description_and_purpose>

Problem: Automated analysis leaves gaps — ambiguous domain logic, unstated conventions, missing rationale.
Validation: Every accumulated gap has a resolution; each answer traces to at least one file update.

</description_and_purpose>

<workflow_context>

- Phase 7 of 8 in init-workspace-flow
- Input: all docs from Phases 1–6, accumulated gaps from state
- Output: answers integrated into docs, affected files updated via subagents

</workflow_context>

<phase_steps>

1. Read state and accumulated gaps
2. Review all created docs for ...

Command Content

Other plugins with /init-workspace-flow-questions

/discuss-phase

57.5k

Gathers phase context via adaptive questioning on gray areas after loading prior decisions, scouting codebase, and outputs {phase_num}-CONTEXT.md. Supports --all, --auto, --chain, --power flags.

9 tools

gsd-build-get-shit-done

/hatch3r-revision

Revises agent-implemented code in fresh context window: reconstructs from git diff, interviews user for feedback, fixes issues, cleans leftovers, runs quality pipeline toward merge readiness.

hatch3r

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_questions> <description_and_purpose> Problem: Automated analysis leaves gaps — ambiguous domain logic, unstated conventions, missing rationale. Validation: Every accumulated gap has a resolution; each answer traces to at least one file update. </description_and_purpose> <workflow_context> - Phase 7 of 8 in init-workspace-flow - Input: all docs from Phases 1–6, accumulated gaps from state - Output: answers integrated into docs, affected files updated via subagents </workflow_context> <phase_steps> 1. Read state and accumulated gaps 2. Review all created docs for ...

<init_workspace_flow_questions>

<description_and_purpose>

Problem: Automated analysis leaves gaps — ambiguous domain logic, unstated conventions, missing rationale. Validation: Every accumulated gap has a resolution; each answer traces to at least one file update.

</description_and_purpose>

<workflow_context>

Phase 7 of 8 in init-workspace-flow
Input: all docs from Phases 1–6, accumulated gaps from state
Output: answers integrated into docs, affected files updated via subagents

</workflow_context>

<phase_steps>

Read state and accumulated gaps
Review all created docs for gaps and contradictions
Ask user reflective questions (bootstrap-hitl-questioning rules)
Map answers to affected files
Spawn one built-in subagent per affected file: answer content, target path, update instructions, preserve-human-content
Verify subagent updates
Update state — clear resolved gaps, note unresolved

</phase_steps>

Do not re-ask questions answered as in-phase blockers — check state
Unanswered questions: log as deferred gap, do not guess

</init_workspace_flow_questions>