What is project-brief?

A command that turns a technical specification into a short summary for project managers and technology leaders. It focuses on business value, architecture, plans, risks, timelines, and decisions rather than implementation detail.

Use it to create an executive brief from a readable technical specification, including the project overview, simplified architecture, roadmap, alternatives, risks, timeline, and immediate actions.

It removes low-level engineering detail that can make a technical specification hard for non-engineers to use. It also keeps important project information in a format suited to planning and review.

project-brief — Command for Claude Code by hmj1026: A command that turns a technical specification into a…

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/hmj1026/dhpk/project-brief

Clone the repo

git clone --depth 1 https://github.com/hmj1026/dhpk

Made for: Claude Code.

Or install dhpk, the plugin that ships this one along with the rest of its 65 skills, 31 commands, 40 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/hmj1026/dhpk/project-brief.svg)](https://agentmods.dev/commands/hmj1026/dhpk/project-brief)

Your own site

<a href="https://agentmods.dev/commands/hmj1026/dhpk/project-brief"><img src="https://agentmods.dev/badge/commands/hmj1026/dhpk/project-brief.svg" alt="Measured on agentmods" height="20"></a>

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 783 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.00783
Opus 5	$0.00012	$0.00392
Sonnet 5	$0.00005	$0.00157
Haiku 4.5	$0.00002	$0.00078

Measured today against content hash 8bacf370eb98, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

project-brief scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured today.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/project-brief.md · 132 lines

How it starts

The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Contract

Use to convert a readable technical spec into an executive brief; not to edit the source spec. See the command contract. Stop when the source is missing or unreadable; completion reports the output path and unresolved decisions retained for review.

Context

Project root: !git rev-parse --show-toplevel

Task

You are now a brief-writer expert. Convert the technical spec into a PM/CTO-readable executive summary.

Input

$ARGUMENTS

Conversion Rules

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

Execution Flow

Step 1: Read Technical Spec

Read the specified tech spec file
Identify the core value proposition

Step 2: Extract Key Information

Project overview: one sentence on what, why, and value
Current state vs target comparison
Solution evaluation (keep pros/cons comparison)
Milestone timeline
Risk summary
Resource requirements

Step 3: Simplify Technical Details

Remove code snippets
Remove internal module names
Remove technical implementation details
Keep business logic descriptions

Step 4: Produce Executive Summary

Output

Produce a PM/CTO-readable executive summary in the following format:

# [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 |
| --------------- | ---- | ---- | -------------- |
| Option A        |      |      |                |
| Option B        |      |      |                |
| Recommended     |      |      | ✅ Adopt       |

## Architecture Overview

(Simplified system diagram, 3 layers max)

## Milestones

| Week   | Deliverable | Dependencies |
| ------ | ----------- | ------------ |
| Week 1 |             |              |
| Week 2 |             |              |

## Risk Summary

| Risk | Impact Level | Mitigation |
| ---- | ------------ | ---------- |
|      |              |            |

## Resource Requirements

- **Headcount**:
- **Timeline**:
- **External Dependencies**:

## Decision Points

> Items requiring PM/CTO decision

- [ ] Decision 1:
- [ ] Decision 2:

Read the full file on GitHub · 132 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

today First seen · 132 lines · 24 tokens per session scan A 8bacf370eb98

Subscribe to this mod's changes

project-brief is a command published in the GitHub repository hmj1026/dhpk (2 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 783 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.

OpenSpec Project management Writing and docs ai-tooling claude-code claude-code-plugin harness

project-brief