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.