メニュー
Use for portal-heavy work: Gin handlers, middleware, templates, SSE flows, dashboard pages, auth, sessions, CSRF wiring, and user-visible portal behavior.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when asked to work in a continuous loop until done or truly blocked. Orchestrates pickup, planning, TDD execution, implementation waves when needed, debugging side-chains, verification, and resume behavior.
Use before planning when a feature or change request is underspecified. Resolve high-impact ambiguity around scope, consumers, security, failure handling, and acceptance criteria before writing the implementation plan.
Use for both preparing work for review and responding to review feedback. Keep review evidence local, concrete, and scoped to the real contract. Verify technically before agreeing or changing code.
Use before implementation. Merge design discovery and plan writing into one DR-specific flow: identify the consumer, inspect the repo, debate boundaries with partner and combatant, and produce an execution-ready plan that hands off cleanly into DR-native tasks, TDD, and implementation waves.
Use for the last mile: rerun verification, inspect diffs, commit or push if requested, and perform local docker-compose checks when needed. This is the DR local-tools replacement for MCP-style finish/deploy carryovers.
Use after planning and before implementation when you need a concrete, dependency-ordered task list. Turn the DR feature spec and plan into independently testable task slices with exact file paths and verification commands.
| name | dr-portal-ui-and-handlers |
| version | 2026-03-26.1 |
| description | Use for portal-heavy work: Gin handlers, middleware, templates, SSE flows, dashboard pages, auth, sessions, CSRF wiring, and user-visible portal behavior. |
The change touches:
portal/main.goLoad dr-repo-reference first for shared portal checks and component verification commands.
Use the portal entries from dr-repo-reference.
Always consider:
portal/main.goFor large portal tasks:
portal_explorer first to map routes, middleware, templates, and testsreviewer for correctness review once the change is understoodsecurity_reviewer if auth, admin, session, CSRF, token, or download behavior is involvedUse the model and reasoning defaults from docs/CODEX_AGENT_POLICY.md instead of treating all portal subagent work as the same cost or depth.