shinpr/codex-workflows

recipe-add-integration-tests

Add integration/E2E tests to existing codebase using Design Docs.

原文の言語: 英語

recipe-build

Execute an approved backend Work Plan autonomously through task execution, quality fixes, commits, and final verification.

原文の言語: 英語

recipe-design

Execute from codebase-scoped analysis to design document creation.

原文の言語: 英語

recipe-diagnose

Investigate problem, verify findings, and derive solutions through structured diagnosis.

原文の言語: 英語

recipe-front-adjust

Adjust an implemented UI with focused evidence, verification, and quality checks.

原文の言語: 英語

recipe-front-build

Execute an approved frontend Work Plan autonomously through frontend implementation, quality fixes, commits, and final verification.

原文の言語: 英語

recipe-front-design

Execute from codebase-scoped analysis to frontend design document creation including UI Spec.

原文の言語: 英語

recipe-front-plan

Create frontend work plan from design document with test skeleton generation.

原文の言語: 英語

recipe-front-review

Reviews completed frontend implementation for governing-source compliance, scope economy, repository quality, and security, and applies user-approved React corrections.

原文の言語: 英語

recipe-fullstack-build

Execute an approved fullstack Work Plan autonomously with layer-aware task routing, quality fixes, commits, and final verification.

原文の言語: 英語

recipe-fullstack-implement

Run the full-cycle implementation workflow for one outcome spanning backend and frontend layers.

原文の言語: 英語

recipe-implement

Orchestrate the complete implementation lifecycle from requirements through verified repository implementation.

原文の言語: 英語

recipe-plan

Creates a reviewed Work Plan with value-filtered integration/E2E test skeletons. Use when planning implementation from a Design Doc.

原文の言語: 英語

recipe-prepare-implementation

Prepare repository-local execution tools when the user requests setup or a concrete build capability is unavailable.

原文の言語: 英語

recipe-quality-profile

Proposes and, after user confirmation, creates or maintains docs/project-context/quality.yaml from repository-specific review requirements. Use when asked to generate or update a repository quality profile.

原文の言語: 英語

recipe-reverse-engineer

Generate PRD and Design Docs from existing codebase through discovery, generation, verification, and review.

原文の言語: 英語

recipe-review

Reviews completed implementation for governing-source compliance, scope economy, repository quality, and security, and applies user-approved corrections.

原文の言語: 英語

recipe-update-doc

Update existing design documents (Design Doc / PRD / ADR) with review and consistency verification.

原文の言語: 英語

documentation-criteria

Determines which PRD, ADR, UI Spec, Design Doc, and Work Plan a change requires and where each document lives. Use when deciding documentation scope or creating or reviewing one of these artifacts.

原文の言語: 英語

llm-friendly-context

Clarifies inputs, outputs, success criteria, decisions, and unresolved conditions so downstream agents can execute without guessing. Use when writing or revising LLM-facing prompts, handoffs, planning artifacts, reviews, reports, or generated instructions.

原文の言語: 英語

subagent-delegation

Sets delegation scope, completion waiting, and evidence-based intervention. Use when spawning, waiting for, or steering any subagent, including a single ad hoc agent or a custom workflow agent.

原文の言語: 英語

subagents-orchestration-guide

Coordinates custom specialists through workflow phases, artifact handoffs, approval gates, and autonomous implementation. Use when executing a workflow recipe or routing its next specialist.

原文の言語: 英語

implementation-approach

Selects the smallest sufficient implementation strategy and verification boundary from current requirements and repository evidence.

原文の言語: 英語

integration-e2e-testing

Selects and specifies the integration/E2E tests that own accepted behavior at the boundary where it is observable.

原文の言語: 英語

requirement-convergence

Converges future-state requirements around outcome, exclusions, and rough cost. Use when users ask 'do we need this?', 'how far should we go?', or request a feature or scope change.

原文の言語: 英語

reviewee-judgment

Evaluates received review results before they generate work by separating problems from proposed fixes and comparing responses in a fixed decision order. Use whenever review results may lead to artifact changes; does not produce reviews.

原文の言語: 英語

testing

Repository-aware rules for choosing which tests a change needs, one owning test per claim, observable proof, and test integrity. Use when writing, reviewing, or fixing tests.

原文の言語: 英語

recipe-outcome-watch

Monitors development work against its governing outcome at a user-selected interval. Use when asked for periodic independent checks for scope drift or unnecessary work.

原文の言語: 英語

ai-development-guide

Root-cause discipline, proportionate impact analysis, and implementation completeness assurance. Use when fixing bugs, reviewing code quality, refactoring, making technical decisions, or performing quality assurance.

原文の言語: 英語

coding-rules

Repository-aware implementation rules for minimal design surface, contract safety, representative patterns, and verifiable changes. Use when implementing, refactoring, or reviewing code.

原文の言語: 英語

external-resource-context

Resolves and records one external evidence source required by a current design or verification decision. Use when repository and supplied evidence cannot determine that decision.

原文の言語: 英語