From sd0x-dev-flow
Converts technical specs into PM/CTO-readable executive summaries. Simplifies technical details, focuses on business value, outputs structured markdown.
How this skill is triggered — by the user, by Claude, or both
Slash command
/sd0x-dev-flow:project-briefThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
- Keywords: executive summary, project brief, PM summary, CTO summary, project-brief
/fp-brief)/tech-spec)/codex-review-doc)Agent({
description: "Convert technical spec into PM/CTO executive summary",
subagent_type: "brief-writer",
prompt: `Convert the following tech spec into a PM/CTO-readable executive summary.
Follow the conversion rules and execution flow defined in this skill.`
})
$ARGUMENTS
| Tech Spec Section | PM/CTO Summary Treatment |
|---|---|
| Trust boundary diagram | Simplify to 3-layer arch |
| Code analysis | Remove |
| Reusable modules | Remove |
| System architecture | Keep (simplified) |
| Implementation roadmap | Keep |
| Key design decisions | Remove |
| Alternative comparison | Keep |
| Risks & mitigations | Keep |
| Timeline | Keep |
| Immediate actions | Simplify to decision points |
# [Project Name] Executive Summary
## Project Overview
> One sentence: what, why, and value
## Current State vs Target
| Dimension | Current | Target |
|-----------|---------|--------|
## Solution Evaluation
| Solution | Pros | Cons | Recommendation |
|----------|------|------|----------------|
## Architecture Overview
(Simplified system diagram, 3 layers max)
## Milestones
| Week | Deliverable | Dependencies |
|------|-------------|--------------|
## Risk Summary
| Risk | Impact Level | Mitigation |
|------|-------------|------------|
## Resource Requirements
- **Headcount**:
- **Timeline**:
- **External Dependencies**:
## Decision Points
> Items requiring PM/CTO decision
- [ ] Decision 1:
- [ ] Decision 2:
By default, save to the same directory as the original file with a -brief suffix.
Example: docs/features/xxx/architecture.md -> docs/features/xxx/architecture-brief.md
If $ARGUMENTS contains --output <path>, save to the specified location.
npx claudepluginhub sd0xdev/sd0x-dev-flow --plugin sd0x-dev-flowUse this skill when the user asks to "write an engineering brief", "brief the engineering team", "write a technical spec handoff", "summarize this PRD for engineers", "engineering kickoff doc", "write a spec for the dev team", "help me communicate this feature to engineering", or needs to translate a product decision or PRD into an engineering-ready communication that gives engineers the context to make good technical decisions.
Translates technical documents (API specs, architecture docs, RFCs, proposals) into PM-actionable language on product/user impacts, decisions, risks, and questions to ask engineering.
Condenses a long output, report, or analysis into a scannable one-page executive brief — conclusion first, key facts, business impact. Useful when the user wants the gist of something they don't have time to read fully.