# Feature Brief

> Write a lightweight feature brief or product decision document that records problem, evidence, options, scope, success measures, risks, and recommendation. Use when early exploration or a product decision needs a compact artifact before a full specification or implementation plan.

- Skill: `majesticlabs-dev/feature-brief` (Agent Skill)
- Install (CLI): `npx skillmds@latest add majesticlabs-dev/feature-brief`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majesticlabs-dev/feature-brief/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: majesticlabs-dev (https://skillmd.com/u/majesticlabs-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/majesticlabs-dev/feature-brief

---


# Feature Brief

## Boundary

Produce a decision-ready brief, not a full PRD or implementation plan. Do not hide tradeoffs to fit one page.

## Required Inputs

- Problem, users, evidence, and decision owner
- Options considered and why now
- Proposed scope, exclusions, dependencies, and constraints
- Baseline, success measure, risks, and open questions

## Workflow

1. Choose feature brief for exploration or decision record for a resolved choice.
2. Write the user problem and evidence before the proposed solution.
3. State target users, non-users, current workaround, and desired outcome.
4. Compare credible options, including doing nothing.
5. Define in-scope, out-of-scope, dependencies, and acceptance evidence.
6. Record success measures with baseline, target rationale, and review timing.
7. State recommendation, tradeoffs accepted, owner, next actions, and revisit criteria.
8. Compress repetition, not uncertainty, alternatives, or risk.

## Output

1. **One feature brief or decision record**
2. **Evidence and assumptions**
3. **Scope and success measures**
4. **Recommendation, open questions, and next actions**

## Quality Gate

- The artifact has one explicit decision or ask.
- Problem evidence is distinct from solution belief.
- Scope exclusions are concrete.
- A reviewer can disagree using visible assumptions.