القائمة
Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value.
يُحدَّد Prompt الذي يراجع المصدر أولًا بشكل افتراضي. يمكنك التبديل إلى أمر مباشر أو تنزيل نسخة محلية.
اقرأ SKILL.md وأي ملفات مرافقة يعرضها SkillsMP قبل أن تقرر التثبيت.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
يتجاوز الأمر المباشر Prompt المخصّص للمراجعة. افحص المصدر قبل تشغيله.
npx skills add https://github.com/sd0xdev/sd0x-dev-flow --skill project-briefيبقى الأمر في سطر واحد. مرّر أفقيًا لمراجعته كاملًا قبل النسخ.
تفضّل نسخة محلية؟ نزّل الملفات المتاحة حاليًا لدى SkillsMP.
Project initialization inventory (one-time). Use when: first onboarding a project, rebuilding cache after structural changes. Not for: day-to-day development (read cache directly), finding specific files (use code-explore). Output: project map with entrypoints + test map + next steps.
Claude Code config health check + plugin sync. Use when: auditing .claude/ structure, checking naming, verifying hook setup, detecting plugin version drift, syncing installed assets. Not for: skill quality (use skill-health-check), code review (use codex-code-review). Output: health report + fix recommendations.
Code review using Codex MCP. Use when: PR review, code audit, second opinion on changes. Not for: doc review (use doc-review), security audit (use security-review). Output: severity-grouped findings + merge gate.
استنادا إلى تصنيف SOC المهني
عرض SKILL.md
| name | project-brief |
| description | Convert a technical spec into a PM/CTO-readable executive summary. Simplify technical details, focus on business value. |
| allowed-tools | Read, Grep, Glob, Write, Agent |
/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.