Ryokuman
Community@Ryokuman
Ryokuman provides layered agent-orchestration governance skills for root/project/silo repository hierarchies, PR review gates, and shared runtime lifecycle management.
Agent Skills by Ryokuman
Showing 13 vetted skills indexed across 1 GitHub repositories.
Ryokumanroot-layer-manager
Classifies requests into hierarchy layers and routes issues, tasks, and feedback to correct storage locations.
Ryokumanuser-personality-adaptive-response
Adapts agent responses, option sets, and approval boundaries to recorded user work preferences.
Ryokumanadd-shared-runtime
Registers and prepares shared runtime workspaces for project task silos.
Ryokumangithub-project-intake
Collects and verifies GitHub repository evidence for portfolio and project SSoT documentation.
Ryokumanmain-branch-update-flow
Updates shared SSoT documents through derived work branches and pull requests.
Ryokumanshared-runtime-health-check
Validates project runtime sets and shared server health before lifecycle execution.
Ryokumancodex-pr-review-loop
Automates Codex review request, wait, fix, and re-review loops for GitHub pull requests.
Ryokumanproject-contract-gate
Guides a two-step interview to define product contracts before task creation.
Ryokumanprojects-setup
Scaffolds Project SSoT structures and registers projects in the orchestrator config.
Ryokumanadd-dict
Manages project dictionary terms by deduplicating and adding reusable vocabulary during PR workflows.
Ryokumanmain-v3-pr-scope-gate
Validates branch names and diff scope before creating tier-0 pull requests.
Ryokumansilo-runtime-handoff
Writes runtime URLs, E2E steps, and handoff comments on silo pull requests.
Ryokumandelete-shared-runtime
Safely removes or archives shared runtime checkouts after verifying references, git state, and running processes.
Frequently Asked Questions About Ryokuman
FAQPage SchemaWhat tasks can I accomplish with Ryokuman's skills?▼
You can classify requests across root/project/silo layers, gate main-v3/main PRs through Codex review loops, register and health-check shared runtimes, scaffold Project SSoT structures, intake GitHub repo evidence for portfolios, and maintain project terminology dictionaries.
Who should use these skills?▼
Engineers operating a multi-layer agent orchestration system with a root orchestrator, per-project SSoT documents, and task silos. It suits maintainers who enforce branch discipline on main-v3/main and need structured PR review, runtime handoff, and scope-gate procedures.
How do the PR review and scope gates work in practice?▼
Before proposing or pushing work targeting main-v3/main, the scope gate checks project SSoT files, non-system diffs, and branch naming. The review loop then requires a codex-review pass and classifies P2+ findings on the latest head as fixes, defenses, or user decisions.
What prerequisites or dependencies do these skills assume?▼
They assume a GitHub account with gh authentication for repo intake, a root orchestrator repository with a projects structure, layered main-v3/main branches, and optionally shared runtime servers, Docker databases, and vite-harness for E2E verification during silo handoff.
How are shared runtimes managed across task silos?▼
The add-shared-runtime skill registers long-running backend/frontend/worker/mock runtime sets per project, the health-check skill verifies runtime_set presence and server status before E2E runs, and delete-shared-runtime handles archival and approved removal of shared runtime checkouts.