workflow-discovery

스타0

포크0

업데이트2026년 2월 18일 08:20

Discover and refine what to build through repo-aware dialogue and structured requirement capture.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

abpaul

abpaul/codex-compound-engineering

다운로드

Workflow Discovery

Use this skill before planning implementation.

Gather feature context and relevant repo patterns.
Confirm whether the default architecture baseline applies:
- Rails server-rendered app
- Phlex UI components
- Stimulus client behavior
- Turbo/Hotwire Native navigation
- Tailwind + daisyUI usage layered over project semantic tokens (no raw theme shipping)
- project-specific brand palette/fonts/illustration mapped to tokens
- MD3-inspired token system with project-owned palette/type/illustration
- MD3 used as structural guidance only, not copied visual identity
- screenshot-driven polish loop requirement for changed UI surfaces
Ask one question at a time to clarify goals, users, constraints, and success criteria.
Propose 2-3 approaches with tradeoffs and recommendation.
Write discovery output to docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md.
Validate the document for clarity, scope boundaries, and open questions.
Hand off to workflow-plan.

이 저장소의 다른 Skills

같은 저장소

Design, audit, and review agent-native systems to ensure action parity and robust agent workflows.

Upload and sync files to cloud providers using reproducible rclone-based workflows.

Optimize conversion with evidence-tiered layout and copy experiments.

Drive implementation fidelity against design intent through compare-analyze-iterate loops.

Produce and publish project-facing documentation artifacts (changelogs, walkthroughs, release docs).

Create distinctive tokenized UI for Rails server-rendered apps using Phlex, Stimulus, and Turbo/Hotwire Native.

name	workflow-discovery
description	Discover and refine what to build through repo-aware dialogue and structured requirement capture.

Use this skill before planning implementation.

Gather feature context and relevant repo patterns.
Confirm whether the default architecture baseline applies:
- Rails server-rendered app
- Phlex UI components
- Stimulus client behavior
- Turbo/Hotwire Native navigation
- Tailwind + daisyUI usage layered over project semantic tokens (no raw theme shipping)
- project-specific brand palette/fonts/illustration mapped to tokens
- MD3-inspired token system with project-owned palette/type/illustration
- MD3 used as structural guidance only, not copied visual identity
- screenshot-driven polish loop requirement for changed UI surfaces
Ask one question at a time to clarify goals, users, constraints, and success criteria.
Propose 2-3 approaches with tradeoffs and recommendation.
Write discovery output to docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md.
Validate the document for clarity, scope boundaries, and open questions.
Hand off to workflow-plan.