RIC DevFlow Entry

1. Task classification: Complete development within scope enters the full process; explicit

   ric-devflow-<role>

   or precise role delegation only prepares the necessary closure for that role. Explanations, general advice, standalone read-only review/testing, documentation-only edits, minimal risk-free edits, and unrelated Skill requests do not implicitly start the full DevFlow; follow the user's explicit choice.
2. Host and identity: Confirm Codex, Claude Code, or ZCode and the main/sub session based on actual host declarations, available tools, and native launch context; the existence of a configuration directory is not identity evidence. If unclear, unsupported, or conflicting identity, keep the original task and report the precise gaps. If an already-started sub-role is missing components, only hand back to the host; do not install or derive additional agents.
3. Install scope: Record the logical

   discovered_path

   , trusted candidate

   source_root

   , and

   install_scope

   ; write following the logical discovery path or confirmed scope, not inferred back from symlink realpath. If only a source path exists and the scope is unknown, first determine the scope before writing.
4. Completeness and missing-component guard: First check whether

   references/bootstrap.md

   in this entry and the current platform materials are readable; do not open missing links below before they are ready. When the main session is missing components, first confirm the release source

   https://github.com/lichong-a/ric-dev-workflow-skills

   , preferably a complete trusted local checkout or an installation record with a full SHA; if no record exists, fetch a candidate from the confirmed source once and pin the SHA, without guessing history or executing downloaded code. Verify the type and bytes of every existing package file in this closure against the complete manifest for that SHA; the entry itself must also match. If the source is unknown, the scope is unknown, the candidate is incomplete, customized/divergent, contains unknown files, or has broken links, keep all install targets zero-write and report gaps. After matching, read bootstrap and current platform materials only from the trusted candidate source, list the required Skill closure, required native definitions/config, parent directories, and permissions; do not copy any missing components until conflict, explicit-disable, and permission prechecks for all targets pass; after passing, exclusively create and normal-copy the missing items, re-verify they are still missing before writing, read back verbatim after writing, and re-compare before filling gaps if interrupted. Already-started sub-roles only hand back to the host and do not self-recover. After the files are complete, continue with Preparation and Recovery; full development requires all five Skills and the four native roles of the current host; a standalone role only checks the entry, that role, and necessary transitive references/config, not unrelated roles.
5. Supplement and configuration: Only when components are missing or configuration verification is required, read one current-platform reference per bootstrap: Codex, Claude Code, or ZCode. Pin the trusted candidate SHA, verify the existing package files of the whole closure to be fixed, precheck all targets, then fill only missing items; stop at the original boundaries on conflicts, disablement, and permission denials, and do not execute download/install code.
6. Load verification: Report file installation, host loading, and actual invocation separately. File completeness does not mean the role is loaded; if able to continue, proceed along the original task. When reload is needed, provide minimal recovery information, do not re-install, and do not fake successful invocation or business Gate.
7. Role routing: Read the target role entry only after readiness. Codex's Root Planner remains directly scheduled; Claude/ZCode main sessions forward via native peer invocation, the sole Planner makes decisions and writes state, and the four sub-roles do not derive agents. If the role tool is unavailable or the target is not loaded, report gaps; do not impersonate with a generic agent.

ric_devflow_planner

ric-devflow-planner

ric_devflow_reviewer

ric-devflow-reviewer

ric_devflow_tester

ric-devflow-tester

ric_devflow_implementer

ric-devflow-implementer