メニュー
Use when running, editing, or troubleshooting the packaged claude-code-deepdesign rielflow workflow for design-doc specification authoring with deep and broad review loops.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | riel-claude-code-deepdesign |
| description | Use when running, editing, or troubleshooting the packaged claude-code-deepdesign rielflow workflow for design-doc specification authoring with deep and broad review loops. |
Use this skill when the user asks Claude Code to create or refine design-doc specifications through the packaged claude-code-deepdesign workflow, or when maintaining that workflow package.
claude-code-deepdesignclaude-code-deepdesignclaude-code-agentdesign-docs/ specification plus deep and broad review summarieshigh or middle findingsRun from the repository root after checkout or installation:
rielflow workflow run claude-code-deepdesign \
--variables '{"workflowInput":{"feature":"Describe the feature to design.","targetDesignDoc":"design-docs/specs/design-example.md","constraints":["Design documentation only."],"acceptanceCriteria":["Deep review has no high or middle findings.","Broad review has no high or middle findings."]}}' \
--output json --no-auto-improve
Adjust feature, targetDesignDoc, targetScope, constraints, acceptanceCriteria, and nonGoals to the user's request.
The workflow should not stop for user confirmation. When a user decision would normally be required, Node 1 must choose the generally preferable, conservative specification and document it as a provisional decision.
Each provisional decision should include:
Prefer recording these decisions in a clearly named Provisional Decisions section of the target design document. Use design-docs/user-qa/ when the decision needs a separate follow-up note.
Node 2 deep review checks assumptions, prerequisites, irregular states, lifecycle edge cases, recovery paths, malformed inputs, permissions, privacy, observability, and testability.
Node 3 broad review checks existing similar features, duplication risk, adjacent workflow behavior, package and installation impacts, combined use cases, compatibility, migration, docs, and repository conventions.
Both reviewers must return adapter JSON with when.needs_revision and payload.needs_revision. Set those booleans to true only when any high or middle finding exists.
Validate the package workflow after edits:
rielflow workflow validate claude-code-deepdesign \
--workflow-definition-dir ./packages/claude-code-deepdesign/workflows
Run the bundled mock scenario when prompts, transitions, or review payloads change:
rielflow workflow run claude-code-deepdesign \
--workflow-definition-dir ./packages/claude-code-deepdesign/workflows \
--mock-scenario ./packages/claude-code-deepdesign/workflows/claude-code-deepdesign/mock-scenario.json \
--output json
Refresh rielflow-package.json digests after changing the workflow or packaged skill:
bun .agents/skills/rielflow-package-release/scripts/update-package-digests.ts claude-code-deepdesign
Use when implementation work in a rielflow project changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the packaged `claude-code-design-and-implement-review-loop` workflow, including design/plan alignment, implementation, review, user-facing documentation refresh, commit-message generation, and built-in git commit/push steps.
Use when implementation work in a rielflow project changes behavior, adds functionality, or fixes bugs and the user has not explicitly asked to avoid workflows. Routes the work through the packaged `codex-design-and-implement-review-loop` workflow, including design/plan alignment, implementation, review, user-facing documentation refresh, commit-message generation, and built-in git commit/push steps.
Use when requested work should first be converted into a project-scope Rielflow workflow and then executed through Rielflow. Applies to workflow-first implementation, review, refactoring, documentation, or maintenance tasks where no existing package workflow exactly fits, and to requests that explicitly say to work through a project-scope workflow.
Use when requested work should first be converted into a project-scope Rielflow workflow and then executed through Rielflow. Applies to workflow-first implementation, review, refactoring, documentation, or maintenance tasks where no existing package workflow exactly fits, and to requests that explicitly say to work through a project-scope workflow.
Use when installing a rielflow workflow bundle from a public GitHub directory URL with workflow checkout. Covers project/user scope destinations, duplicate handling, overwrite behavior, registry metadata, validation, and checkout troubleshooting.
Use when running a generic Claude Code Opus 4.8 workflow that creates and reviews a goal, creates and reviews an in-session plan without plan files, performs the work, and reviews whether the goal is achieved before looping back to work or planning.