skills.rest
LeroyAdonis
LeroyAdonisCOMMUNITY
Explore all skills by this author →
GitHub

brief

Generates a read-only briefing on a build-plan feature before spec'ing it.

Updated Mar 2, 2026
Search Tags:#workflow#project planning#dependency analysis#build plan#read-only#feature briefing#spec preview
One-click install
npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill brief-leroyadonis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brief
Source: https://github.com/LeroyAdonis/kitfix-2.0/tree/main/.agents/skills/brief
Command: npx skills add https://github.com/LeroyAdonis/kitfix-2.0 --skill brief-leroyadonis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before committing to spec a feature, you often need to understand what it involves, what it depends on, and how big it is. This Skill reads your build plan and project overview and produces a concise, read-only briefing so you can decide whether to spec, reorder, split, or clear a blocker first. ## Core Features & Use Cases - Feature Briefing: Explains what a feature is, what it depends on, what it unblocks, what files and systems it touches, and its likely size. - Split Prediction: Flags whether a large feature will likely split into sub-items (e.g., 5a, 5b, 5c) before you run the spec step. - Blocker Detection: Honestly reports missing prerequisites, stub plans, or stale overviews instead of inventing scope. - Use Case: Run /brief 5 to preview the submission draft flow feature, learn it depends on an unbuilt API backend, and decide to clear that blocker before running /feature 5. ## Quick Start Ask the assistant to brief the next unchecked feature in build-plan.md, or specify one by number or name such as "/brief 4".

Frequently Asked Questions about brief

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

FAQPage Schema
How do I preview a feature before writing a spec for it?▼

Run the brief command with a feature number or name, such as /brief 4 or /brief "validator". It reads build-plan.md and project-overview.md and returns a short briefing covering scope, dependencies, size, and open questions without writing anything.

What is the difference between brief, feature, and status commands?▼

The brief command gives a read-only, in-depth explanation of one feature. The feature command writes the actual spec and may split the item in build-plan.md. The status command reports on the whole project rather than a single feature.

Does the brief command modify build-plan.md or create branches?▼

No, it is strictly read-only. It never writes files, edits build-plan.md or current-feature.md, creates branches, commits, installs, or builds. To act on a briefing, you run the feature command next.

What happens if build-plan.md is empty or the project overview is missing?▼

The briefing stops and tells you plainly that the plans are a stub or the overview is missing, pointing you to fill them in first. It does not invent a briefing from missing context.

Can brief tell me if a feature is too large to spec at once?▼

Yes, the briefing includes a size estimate and predicts likely sub-splits, such as breaking a feature into 5a, 5b, and 5c. This helps you decide whether to spec it directly or split it first.

Related Skills

Explore More Software Engineering Skills→
tense-itense-i
1

architecture-validator

Validate plan.md completeness and alignment with feature specifications.

Community
Advanced
liqiongyuliqiongyu
51

writing-specs-designs

Generate spec and design document packs for product features and UX changes.

Community
Advanced
MichaelsEngineeringMichaelsEngineering

gpd-progress

Reports research progress and routes to the next GPD workflow action.

Community
Advanced
leeoveryleeovery
27

start-feature

Generate a feature specification markdown file from inline context.

Community
Basic