Runs CEO → design → eng review: no actionable steps/tasks for build

[seanlabs]

I am running office-hours, CEO, design, and eng-review skills, but reviewing the *.md output I don't see any actionable content that would steer Claude Code on what to build. I was expecting more broken down components and steps into a task list that would drive the Claude Code or Codex build.

[Hchumpitaz]

For software development, I also recommend using OpenSpec (https://github.com/Fission-AI/OpenSpec).

OpenSpec is a Spec-Driven Development (SDD) framework that resides in openspec/ within your repository. Its purpose: to allow you and the AI ​​to agree on what will be built before touching any code, by writing specs in Markdown that then become the source of truth for the system's behavior.

openspec/
├── specs/ # Source of truth (your system's behavior)
│ └── /spec.md
├── changes/ # Proposed updates (one folder per change)
│ └── /
│ ├── proposal.md # Why and what
│ ├── design.md # How (technical)
│ ├── tasks.md # Implementation Checklist
│ └── specs/ # Delta specs (what's changing)
└── config.yaml # Proyect configuration (optional)