跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
设计与 UI

recipe-design

Execute from codebase-scoped analysis to design document creation.

shinpr · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add shinpr/codex-workflows --skill recipe-design

技能说明


name: recipe-design description: "Execute from codebase-scoped analysis to design document creation."

Required Skills [LOAD BEFORE EXECUTION]

  1. [LOAD IF NOT ACTIVE] documentation-criteria — document creation rules and templates
  2. [LOAD IF NOT ACTIVE] implementation-approach — design convergence and verification strategy
  3. [LOAD IF NOT ACTIVE] subagents-orchestration-guide — agent coordination and review resolution
  4. [LOAD IF NOT ACTIVE] llm-friendly-context — document and review handoffs

Spawn rule: every spawn_agent call uses fork_turns="none" so the subagent receives only the task message and explicitly provided context.

Context: Dedicated to the design phase.

Orchestrator Definition

Core Identity: Coordinate design, make workflow decisions from compact specialist materials, and invoke specialists for analysis, authoring, and review.

Execution Plan: Reuse the active execution plan. When the workflow has multiple dependent actions and no plan exists, create one that tracks them through final verification.

Execution Protocol:

  1. Spawn agents for analysis and document work -- your role is to invoke sub-agents, select from their compact evidence against governing requirements, pass the selected material onward, and report results.
  2. Run the design flow below in order:
    • Execute: scope evidence -> codebase-analyzer -> [Stop: Scope confirmation] -> optional PRD update/review/[Stop: PRD approval] -> optional ADR batch/batch review/[Stop: ADR-batch approval] -> Design Doc -> code-verifier/Review Resolution -> document-reviewer -> design-sync -> [Stop: Design approval]
    • [STOP — BLOCKING] At every [Stop: ...] marker -> Present status to user for confirmation. CANNOT proceed until user explicitly confirms.
  3. Scope: Complete when design documents receive approval

CRITICAL: MUST execute document-reviewer and all stopping points. MUST execute design-sync for Design Docs. Each serves as a quality gate. ENFORCEMENT: Skipping any quality gate invalidates the design output.

Workflow Overview

Requirements -> scope evidence -> codebase-analyzer -> [Stop: Scope confirmation]
                                                            |
                                      optional PRD update/review -> [Stop: PRD approval]
                                                            |
                                   optional ADR batch/review -> [Stop: ADR-batch approval]
                                                            |
                         Design Doc -> code-verifier -> Review Resolution -> document-reviewer
                                                            |
                                                    design-sync -> [Stop: Design approval]

Scope Boundaries

Included in this skill:

  • Compact scope and cost evidence from requirement-analyzer; the orchestrator owns requirement, scale, and ADR decisions
  • Codebase analysis with codebase-analyzer (entry point of the design phase)
  • Scope confirmation with the user, grounded in codebase-analyzer findings
  • One ADR per qualifying decision point found in the current scope, created and reviewed as one batch
  • Design Doc creation with technical-designer
  • Document review with document-reviewer
  • Design Doc consistency verification with design-sync

Responsibility Boundary: This skill completes with approval of the Design Doc and its preceding ADR when required. Work planning and beyond are outside scope.

Requirements: $ARGUMENTS

ADRs record the considered options and one selected decision. PRDs and Design Docs contain only confirmed requirements and selected conclusions; evaluation-only ideas and unselected design candidates remain in the active workflow context.

Execute the process below within design scope.

Execution Process

Step 1: Scope and Cost Evidence

Spawn requirement-analyzer with the original requirements. Treat exact user quotes according to their returned signal type: implementation requirements and exclusions can enter confirmed scope; evaluation requests, speculation, and prescribed mechanisms remain non-binding until the orchestrator resolves them against the user's wording. Treat scope evidence, cost evidence, and questions as material; the orchestrator determines requirements, scale, and ADR routing.

Step 2: Codebase Analysis

Spawn codebase-analyzer agent: "exploration_mode: [mode from Analysis Assignment]. Analyze the existing codebase to provide compact decision materials for requirement confirmation, ADR selection, minimal Design Doc creation, and verification. requirement_analysis: [Step 1 scopeEvidence]. requirements: $ARGUMENTS. target_paths: [Step 1 scopeEvidence.affectedFiles]."

Step 3: Scope Confirmation

After codebase-analyzer returns, confirm the requirements, determine Structural Scale, and identify qualifying ADR decision points:

  1. Locate a related PRD and read its Converged Outcome, MVP scope, Future / Out of Scope, and open requirement fields. If the related PRD is ambiguous, ask the user to select or provide its path, or confirm none exists, before continuing.
  2. When those fields match the current request and returned scope facts, use the PRD path as the current carrier and proceed directly to scope confirmation.
  3. When a current carrier is absent, load requirement-convergence. The orchestrator builds and judges its record from the user's wording, using Step 1 scope/cost evidence and Step 2 analysis for trade-offs, questions, and routing decisions. Mark an existing but incomplete or scope-mismatched PRD for update; otherwise mark the carrier as absent.
  4. Apply the documentation-criteria Choice filter, then the Durability filter, to Step 2 decisionMaterials.candidateDecisionPoints. adrDecisionPoints contains every current-scope point that passes both filters; an empty array routes directly to Design Doc regardless of scale.
  5. Determine Structural
阅读完整来源 ↗