Agent skill

Fp Brief

by sd0xdev in sd0xdev/sd0x-harness

First-principles briefing from technical documents. An agent skill from sd0xdev/sd0x-harness.

MITAuto-check passedDevelopment

Install Fp Brief

skills CLI
$ npx skills add sd0xdev/sd0x-harness --skill fp-brief -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install sd0xdev/sd0x-harness fp-brief --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/sd0xdev/sd0x-harness.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/fp-brief .claude/skills/fp-brief && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
fp-brief
GitHub stars
192
Token cost
~1.8k tokens
SKILL.md length
534 words
Files
5 (incl. references)
Skills in repo
89
Repo updated
First seen
Licence
MIT

At a glance

First-principles briefing from technical documents. An agent skill from sd0xdev/sd0x-harness.

  • Works in 3 steps: Input Resolution → First-Principles Extraction → Output Assembly
  • : understanding why decisions were made
  • SKILL.md covers Trigger, When NOT to Use, Command Signature and Workflow, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Fp Brief is an agent skill from sd0xdev/sd0x-harness. First-principles briefing from technical documents. Use when: understanding why decisions were made, onboarding to feature reasoning, reviewing decision chains, explaining doc from first principles. Not for: PM/CTO summary (use project-brief), pre-doc analysis (use feasibility-study), code explanation (use codex-explain). Output: structured reasoning chain with sensitivity analysis.

Its SKILL.md is about 1.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/codex-verify-prompt.md`, `references/detection-rules.md` and `references/extraction-guide.md`).

It sits in Development, covering Technical documentation. The repository describes itself as: The harness layer for Claude Code — a reference implementation of harness engineering with hook-enforced dual review, state-machine gates that survive context compaction, and… The licence is MIT.

When your agent uses it

  • : understanding why decisions were made
  • Onboarding to feature reasoning
  • Reviewing decision chains
  • Explaining doc from first principles

Example prompts

  • “/fp-brief”

Requirements

  • Pre-approved tools (allowed-tools): Read, Grep, Glob, Write, Bash(node:*)

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Input Resolution
  2. First-Principles Extraction
  3. Output Assembly

What it can do on your machine

Read from SKILL.md and the folder at commit a4d4bc1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Grep
    • Glob
    • Write
    • Bash(node:*)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are mermaid and markdown).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Fp Brief loads about 1.8k tokens when it runs, and up to ~5.5k if it reads all its reference files. Until then it costs about 99 tokens; SKILL.md has 534 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~99
When it runs · the whole SKILL.md, loaded when a task matches
~1.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from sd0xdev/sd0x-harness at commit a4d4bc1, republished under its MIT licence (© sd0xdev). 534 words, ~1,822 tokens.

Download SKILL.mdSave it as .claude/skills/fp-brief/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
fp-brief
description
First-principles briefing from technical documents. Use when: understanding why decisions were made, onboarding to feature reasoning, reviewing decision chains, explaining doc from first principles. Not for: PM/CTO summary (use project-brief), pre-doc analysis (use feasibility-study), code explanation (use codex-explain). Output: structured reasoning chain with sensitivity analysis.
allowed-tools
Read, Grep, Glob, Write, Bash(node:*)

First-Principles Briefing Skill

Trigger

  • Keywords: first principles, fp brief, why was this decided, reasoning chain, decision sensitivity, explain decisions, assumption analysis, onboarding brief

When NOT to Use

ScenarioAlternative
PM/CTO executive summary (strip technical details)/project-brief
Pre-doc feasibility analysis (before writing spec)/feasibility-study
Code explanation at function/file level/codex-explain
Code architecture overview/code-explore
Simple document summaryAsk Claude directly

Command Signature

/fp-brief <doc-path> [--depth brief|normal|deep] [--verify off|codex] [--output <path>] [--no-save]
FlagDefaultDescription
<doc-path>RequiredSource markdown document path
--depthnormalOutput detail level
--verifyoffIndependent Codex reasoning verification
--outputSame dir, -fp-brief.md suffixCustom output path
--no-savefalsePrint to stdout instead of file

Workflow

mermaid
sequenceDiagram
    participant U as User
    participant S as /fp-brief
    participant D as Source Doc
    participant O as Output File
    participant X as Codex (optional)

    U->>S: /fp-brief <doc-path> [--depth] [--verify]
    Note over S: Phase 1: Input Resolution
    S->>S: Validate path (repo boundary)
    S->>D: Read source document
    S->>S: Redaction scan (fail-safe)
    S->>S: Auto-detect format (hybrid)
    Note over S: Phase 2: First-Principles Extraction
    S->>S: Extract Root Problem (5-Why)
    S->>S: Build Assumptions Register
    S->>S: Build Reasoning Chain
    S->>S: Build Alternative Rejection Log
    S->>S: Build Decision Sensitivity
    S->>S: Identify Open Unknowns
    Note over S: Phase 3: Output Assembly
    S->>O: Write *-fp-brief.md
    alt --verify codex
        S->>X: Independent reasoning verification
        X-->>S: Verification Delta
        S->>O: Append Verification Delta
    end
    S-->>U: Report complete
Phase 1: Input Resolution
  1. Path validation: Normalize, reject .. traversal, enforce repo boundary
  2. Read source document
  3. Redaction scan: High-confidence secret patterns → abort; medium → mask [REDACTED]
  4. Format auto-detection: See references/detection-rules.md
  5. Select extraction template based on detected format
Phase 2: First-Principles Extraction

See references/extraction-guide.md for section-by-section heuristics.

SectionCore Question
Root ProblemWhat fundamental truth makes this problem unavoidable?
Assumptions RegisterWhat are we taking for granted, and why?
Reasoning ChainHow does each decision trace back to a principle?
Alternative Rejection LogWhy do other approaches violate our principles?
Decision SensitivityIf assumption X breaks, which decisions collapse?
Open UnknownsWhat don't we know, and what should we find out?

For long documents (>500 lines): split by ## headings, extract per-section, merge + dedup.

Phase 3: Output Assembly
  1. Apply depth filter (section inclusion matrix)
  2. Apply source citations (reference source doc section headings)
  3. Apply Evidence Insufficient Rule — never fabricate content for thin sections
  4. Write output file (or stdout if --no-save — which --verify codex rejects, see § Save Behavior)
  5. If --verify codex: dispatch verification per references/codex-verify-prompt.md
Show full SKILL.md (257 more words)Show less

Depth Levels

LevelDescriptionSections Included
briefCore reasoning only (~500 words max)Root Problem (full), Assumptions (top 3), Reasoning Chain (key decisions), Sensitivity (top 3)
normalFull reasoning chain (~1500 words max)All 6 sections with citations
deepFull chain + analysis (~2500 words max)All 6 sections + challenge questions, evidence ratings, counterfactual analysis, risk-weighted unknowns

Verification Delta (section 7) appears only when --verify codex is used, at any depth level.

Length policy: These are upper bounds, not targets. If source doc is thin, output will be shorter. The Evidence Insufficient Rule applies: [Evidence insufficient — source doc lacks data for this section].

Output

See references/output-template.md for full template.

markdown
# First-Principles Briefing: <title>

> Source: <path> | Depth: <level> | Format: <type> | Generated: <timestamp>

## 1. Root Problem
## 2. Assumptions Register
## 3. Reasoning Chain
## 4. Alternative Rejection Log
## 5. Decision Sensitivity
## 6. Open Unknowns
## 7. Verification Delta (optional)
Save Behavior
ConditionOutput Path
DefaultSame directory as source, -fp-brief.md suffix
--output <path>Specified path
--no-savestdout only, no file written. Incompatible with --verify codex — refuse the combination and say why: the verification prompt is built around ${OUTPUT_PATH} and instructs Codex to cat that file, so with nothing on disk there is no subject to verify. Run them separately, or drop --no-save for the verified run

Example: docs/features/auth/2-tech-spec.md → docs/features/auth/2-tech-spec-fp-brief.md

Verification

  • Input path validated (repo boundary enforced)
  • Secret redaction scan executed
  • Format auto-detection result shown in output header
  • Each Reasoning Chain decision cites source section (Source: §<ref>)
  • Each Assumptions Register entry has confidence level
  • Decision Sensitivity maps assumptions to affected decisions
  • Evidence Insufficient markers used where source data is thin
  • Output length within depth-level upper bound
  • If --verify codex: Codex researched independently (per codex-invocation rules)

References

  • Output template: references/output-template.md
  • Detection rules: references/detection-rules.md
  • Extraction guide: references/extraction-guide.md
  • Codex verification: references/codex-verify-prompt.md

Examples

Input: /fp-brief docs/features/seek-verdict/2-tech-spec.md
Action: Read spec → detect tech-spec → extract 6 sections → write 2-tech-spec-fp-brief.md

Input: /fp-brief docs/features/auth/2-tech-spec.md --depth brief
Action: Read spec → extract Root Problem + top assumptions + key decisions + top sensitivity → brief output

Input: /fp-brief docs/features/auth/2-tech-spec.md --depth deep --verify codex
Action: Read spec → full extraction → Codex independent verification → write with Verification Delta

Input: /fp-brief notes/design-decisions.md --no-save
Action: Read doc → detect unknown format → generic extraction → print to stdout

© sd0xdev, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/fp-brief of sd0xdev/sd0x-harness.

  • SKILL.md
  • references/codex-verify-prompt.md
  • references/detection-rules.md
  • references/extraction-guide.md
  • references/output-template.md

Open the folder on GitHubat commit a4d4bc1

Compare with similar skills

Fp Brief next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Fp Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fp Brief this skillsd0xdev/sd0x-harness192—~1.8kAutomated safety check: PassMIT
Diagram Designcathrynlavery/diagram-design45k1 repos~7.5kAutomated safety check: PassMIT
Simple Englishmoeru-ai/airi50k2 repos~4.6kAutomated safety check: PassMIT
Get API Docs with chubandrewyng/context-hub14k2 repos~775Automated safety check: PassMIT
Doc SyncJetBrains/ideavim10k2 repos~2.6kAutomated safety check: PassMIT
Mailspring App ScreenshotsFoundry376/Mailspring18k—~1.5kAutomated safety check: PassGPL-3.0

Similar skills

  • Diagram Design

    cathrynlavery/diagram-design

    Creates branded diagrams, from architecture, flowchart and sequence to charts and maps, as self-contained HTML with inline SVG, with import from draw.io, Mermaid and Excalidraw.

    45k GitHub starsUsed in 1 repo~7.5k tokens
    DevelopmentAuto-check passed
  • Simple English

    moeru-ai/airi

    Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop.

    50k GitHub starsUsed in 2 repos~4.6k tokens
    DevelopmentAuto-check passed
  • Get API Docs with chub

    andrewyng/context-hub

    Fetches current documentation for third-party APIs and SDKs with the chub CLI before the agent writes code against them, instead of relying on remembered API shapes.

    14k GitHub starsUsed in 2 repos~775 tokens
    DevelopmentAuto-check passed
  • Doc Sync

    JetBrains/ideavim

    Official

    Keeps IdeaVim documentation in sync with code changes. An agent skill from JetBrains/ideavim.

    10k GitHub starsUsed in 2 repos~2.6k tokens
    DevelopmentAuto-check passed
  • Mailspring App Screenshots

    Foundry376/Mailspring

    Captures screenshots of the running Mailspring dev app for docs, PRs or visual checks by launching it with a debugging port, driving the UI and clipping to an element.

    18k GitHub stars~1.5k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Draw.io Diagram Studio

    Agents365-ai/drawio-skill

    Creates and edits editable draw.io diagrams from descriptions, code, infrastructure files, SQL and API schemas, with sync, review, test and export tools.

    10k GitHub stars~2.4k tokensUpdated 6 days ago
    DevelopmentAuto-check: notes

More from sd0xdev/sd0x-harness

All 89 skills in this repo
  • Adr

    sd0xdev/sd0x-harness

    Write an Architecture Decision Record (ADR) for a feature — Context / Decision / Status / Consequences / Alternatives, filed as docs/features/<feature/adr-<NNN-<title.md with a 3-digit zero-padded…

    192 GitHub stars~4.8k tokensUpdated yesterday
    Auto-check passed
  • Load PR Review

    sd0xdev/sd0x-harness

    Load GitHub PR review comments into AI session — analyze, triage, plan.

    192 GitHub stars~4.4k tokensUpdated yesterday
    Auto-check passed
  • Next Step

    sd0xdev/sd0x-harness

    Change-aware next step advisor. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Obsidian CLI

    sd0xdev/sd0x-harness

    Obsidian vault integration via official CLI. An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Orchestrate

    sd0xdev/sd0x-harness

    Agent-driven workflow orchestration (v1 report-only). An agent skill from sd0xdev/sd0x-harness.

    192 GitHub stars~2.5k tokensUpdated yesterday
    Auto-check passed
  • PR Comment

    sd0xdev/sd0x-harness

    Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review.

    192 GitHub stars~1.5k tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Fp Brief

What does Fp Brief do?

First-principles briefing from technical documents. An agent skill from sd0xdev/sd0x-harness. Fp Brief is an agent skill from sd0xdev/sd0x-harness. First-principles briefing from technical documents.

When should I use Fp Brief?

Fp Brief fits situations like: : understanding why decisions were made; onboarding to feature reasoning; reviewing decision chains; explaining doc from first principles.

How do I install Fp Brief in Claude Code?

Run `npx skills add sd0xdev/sd0x-harness --skill fp-brief -a claude-code`. Or copy the skill folder (skills/fp-brief in sd0xdev/sd0x-harness) into .claude/skills/fp-brief in your project. Claude Code loads it when a task matches its description.

How do I install Fp Brief in Codex?

Run `npx skills add sd0xdev/sd0x-harness --skill fp-brief -a codex`. Or copy the skill folder (skills/fp-brief in sd0xdev/sd0x-harness) into .agents/skills/fp-brief in your project. Codex loads it when a task matches its description.

Can I use Fp Brief in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add sd0xdev/sd0x-harness --skill fp-brief -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fp-brief, .gemini/skills/fp-brief, .github/skills/fp-brief and .opencode/skills/fp-brief in your project.

What does Fp Brief need to run?

SKILL.md names no scripts, command-line tools or credentials: Fp Brief is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Grep, Glob, Write, Bash(node:*).

Does Fp Brief access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fp Brief safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Fp Brief use?

Fp Brief is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Fp Brief use?

About 1.8k tokens (SKILL.md is roughly 7.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.7k tokens, read only when the agent opens those files.

What are the alternatives to Fp Brief?

Skills that share tags, products or a category with Fp Brief: Diagram Design (cathrynlavery/diagram-design, 45k stars), Simple English (moeru-ai/airi, 50k stars), Get API Docs with chub (andrewyng/context-hub, 14k stars) and Doc Sync (JetBrains/ideavim, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fp Brief?

sd0xdev (a GitHub user) maintains it in sd0xdev/sd0x-harness, which has 192 GitHub stars. The repository holds 89 skills in this directory. The repository was last updated on October 8, 2026.

Source: sd0xdev/sd0x-harness on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.