skills.rest
sd0xdev
sd0xdevCOMMUNITY
Explore all skills by this author →
𝕏@Develop0xGitHub

project-brief

Convert technical specifications into PM/CTO-readable executive summaries.

189|25|Updated Jan 30, 2026
Search Tags:#documentation#roadmap#executive summary#stakeholder communication#convert#tech spec#project brief
One-click install
npx skills add https://github.com/sd0xdev/sd0x-harness --skill project-brief-sd0xdev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-brief
Source: https://github.com/sd0xdev/sd0x-harness/tree/main/skills/project-brief
Command: npx skills add https://github.com/sd0xdev/sd0x-harness --skill project-brief-sd0xdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Technical specifications are too detailed for executives and product managers who need to make decisions quickly. This Skill converts dense tech specs into concise executive summaries that emphasize business value, risks, milestones, and decision points. ## Core Features & Use Cases - Structured Conversion Rules: Maps each tech spec section (architecture, roadmap, risks, alternatives) to an executive-appropriate treatment, removing code and internal module details. - Standardized Output Template: Produces a consistent summary with project overview, current vs target comparison, solution evaluation, milestones, risks, resources, and decision points. - Flexible Output Location: Saves alongside the source file with a -brief suffix by default, or to a custom path via --output. - Use Case: After writing an architecture spec for a new feature, generate a one-page brief so the CTO can approve the roadmap and flag decision items without reading implementation details. ## Quick Start Ask the agent to convert docs/features/payments/architecture.md into an executive summary for the PM and CTO.

Frequently Asked Questions about project-brief

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a technical spec into an executive summary?▼

Provide the path to your tech spec file and the skill reads it, extracts the value proposition, roadmap, risks, and alternatives, then writes a structured executive summary. Output is saved next to the source file with a -brief suffix.

What sections are removed when summarizing a tech spec?▼

Code snippets, internal module names, reusable module lists, and key design decision details are removed. Architecture is simplified to a three-layer view, while roadmap, risks, timeline, and solution comparisons are kept.

Can I save the executive summary to a custom file path?▼

Yes. Pass --output followed by a path in the arguments to override the default behavior. By default the summary is saved in the same directory as the source spec with a -brief suffix.

When should I not use this executive summary skill?▼

Do not use it for first-principles briefings, writing new technical specs, or document review. Those cases are handled by the fp-brief, tech-spec, and codex-review-doc skills respectively.

What does the executive summary output template include?▼

The template includes project overview, current state vs target table, solution evaluation with pros and cons, simplified architecture, milestone timeline, risk summary, resource requirements, and a checklist of decision points for PM/CTO sign-off.

Related Skills

Explore More Product & Management Skills→
vecearvecear

rfc-generator

Generate RFC documents with standardized sections for proposals and reviews.

Community
Advanced
whmathews15whmathews15
1

feature-decision

Structure feature prioritization decisions and record rationale in a markdown decision document.

Community
Advanced
forgefabrikforgefabrik

requesting-code-review

Review completed code changes against requirements and assess merge readiness.

Community
Intermediate
Garsson-ioGarsson-io

kaizen-prd

Formalize problem space, solution scope, and governance into a durable PRD.

Official
Advanced