New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Brief

by aiblueprinthq in aiblueprinthq/ai-blueprint

Brief an upcoming build-plan feature without writing files. An agent skill from aiblueprinthq/ai-blueprint.

MITAuto-check passed

Install Brief

skills CLI
$ npx skills add aiblueprinthq/ai-blueprint --skill brief -a claude-code

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

GitHub CLI
$ gh skill install aiblueprinthq/ai-blueprint 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/aiblueprinthq/ai-blueprint.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/brief .claude/skills/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
brief
GitHub stars
463
Token cost
~1.3k tokens
SKILL.md length
708 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

Brief an upcoming build-plan feature without writing files. An agent skill from aiblueprinthq/ai-blueprint.

  • Works in 4 steps: The target - the feature's line in… → Full context -… → What already exists - earlier checked… → …
  • Feature previews
  • SKILL.md covers Input, What it reads, Output and Rules, plus 1 more section
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Brief is an agent skill from aiblueprinthq/ai-blueprint. Brief an upcoming build-plan feature without writing files. Explain scope, dependencies, affected areas, size, and likely splits for the next item or a named item. Use for /brief, feature previews, what comes next, or build-order decisions before /feature.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A file-backed, spec-driven AI coding workflow framework for building real software while staying in control. The licence is MIT.

When your agent uses it

  • Feature previews
  • What comes next
  • Build-order decisions before /feature

Example prompts

  • “/brief”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. The target - the feature's line in blueprint/build-plan.md, plus whether
  2. Full context - blueprint/context/project-overview.md: the data model,
  3. What already exists - earlier checked build-plan items and, if useful, git
  4. Design reference - if prototypes/ exists and the feature is UI-facing,

What it can do on your machine

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

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    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

Brief loads about 1.3k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 708 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~66
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

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 aiblueprinthq/ai-blueprint at commit 96222b7, republished under its MIT licence (© aiblueprinthq). 708 words, ~1,304 tokens.

Download SKILL.mdSave it as .claude/skills/brief/SKILL.md (or your agent's skills folder).
name
brief
description
Brief an upcoming build-plan feature without writing files. Explain scope, dependencies, affected areas, size, and likely splits for the next item or a named item. Use for /brief, feature previews, what comes next, or build-order decisions before /feature.

brief - understand a feature before you spec it

Context reuse: Reuse any required file already loaded in project instructions or the current session. Read it again only if absent, changed, or exact current bytes or line references are needed.

Where this sits in the workflow:

build-plan + overview  ->  [brief]  ->  /feature  ->  /implement
(what exists)              (read-only    (spec it)     (build it)
                            explainer)

This skill answers one question: what does this feature actually involve, before I commit to spec'ing it? It reads the two files that describe the work and prints a short briefing so you can decide whether to spec it now, reorder it, split it, or clear a blocker first. It is the read-only precursor to /feature.

It never writes anything: no spec, no edits to build-plan.md, no branch, no commit. /feature is the mutating step that turns a briefing into a spec; this one just explains.

How it differs from its neighbors:

  • /explore investigates an open idea against the code without requiring plans. /brief explains an existing build-plan item.

  • /status reports the whole project: progress, current work, git, next action. /brief zooms into one feature and explains it in depth.

  • /feature writes the spec (and may split the item in build-plan.md). /brief previews what /feature would tackle, changing nothing.

Input

A feature from build-plan.md, by number or name - e.g. /brief 4 or /brief "validator".

With no argument, brief the next one - the first unchecked leaf in build-plan.md, the same target /feature would pick.

If build-plan.md is still a placeholder stub or the overview is missing, say so plainly and point at /overview (or filling the plans) rather than inventing a briefing.

What it reads

Gather these, then synthesize. Don't dump file contents; explain.

  1. The target - the feature's line in blueprint/build-plan.md, plus whether a parent was already split into sub-items (4a, 4b, ...).
  2. Full context - blueprint/context/project-overview.md: the data model, routes/endpoints, stack, UI/UX, conventions, and open questions that touch this feature.
  3. What already exists - earlier checked build-plan items and, if useful, git history, to ground the dependency read (what must be in place first, what this unblocks later).
  4. Design reference - if prototypes/ exists and the feature is UI-facing, note which mockups apply (that /feature will link them and port theme.css).
Show full SKILL.md (205 more words)Show less

Output

A short, scannable briefing, not a wall of text. Aim for something like:

Feature 5 - Submission draft flow
What: maintainers submit a skill by GitHub URL (primary) or zip (fallback);
  drafts are saved before validation runs.
Depends on: apps/api must be stood up first (this is the first feature that
  needs the backend); builds on the Skill / SkillVersion shapes from feature 3.
Unblocks: queue-backed validation (6) and the publishable flow (7).
Touches: new User, Submission, SkillVersion tables (Drizzle); GitHub OAuth;
  POST /submissions; R2 snapshot upload; a React upload island (client).
Size: large - likely splits into 5a (OAuth + maintainer profile), 5b
  (GitHub-URL submission + draft record), 5c (zip upload + R2).
Reference: no prototype for this flow; upload.html covers the later validation
  panel, not this form.
Open questions: apps/api (Hono) is not scaffolded yet - resolve before spec'ing.

Next: run /feature 5 to spec 5a, or clear the apps/api blocker first.

Adapt the lines to the feature; drop any that don't apply. Always end with a single Next action - usually /feature N to spec it, but /overview if the plans aren't ready, /prototype if it's UI-facing and the look isn't locked, or "clear X first" when a dependency blocks it.

Rules

  • Read-only, always. Never write a file, never edit build-plan.md or current-feature.md, never branch, commit, install, or build. To act on the briefing, the user runs /feature next.
  • Explain, don't spec. Size, dependencies, and a likely sub-split are the value here; the actual build steps are /feature's job. Don't write step lists.
  • Trace to the plans. Everything in the briefing comes from build-plan.md and project-overview.md. Don't invent scope; if something is underspecified, say so and flag it as a question for /feature or /overview.
  • Be honest about gaps. If the plans are a stub, the overview is stale, or a dependency isn't built yet, say that plainly - catching a blocker before spec'ing is half the value.

Formatting

Format the output to match the project's conventions in blueprint/context/ai-interaction.md: concise, scannable markdown, with lists for enumerations and tables for matrices rather than dense paragraphs.

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

Files

Just SKILL.md in .agents/skills/brief of aiblueprinthq/ai-blueprint.

Open the folder on GitHubat commit 96222b7

Compare with similar skills

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.

Brief compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Brief this skillaiblueprinthq/ai-blueprint463—~1.3kAutomated safety check: PassMIT
Briefalirezarezvani/claude-skills28k—~967Automated safety check: PassMIT
Briefdavepoon/buildwithclaude3.6k—~1.3kAutomated safety check: NotesMIT
Review Briefevery-app/open-seo23k—~1.2kAutomated safety check: PassMIT
Traderspy Market Briefingsickn33/agentic-awesome-skills47k1 repos~2kAutomated safety check: PassMIT
Briefsuboss87/FDEOps957—~339Automated safety check: PassMIT

Similar skills

  • Brief

    alirezarezvani/claude-skills

    /cs:brief <topic — Generate a one-page strategy brief from an office-hours intake.

    28k GitHub stars~967 tokensUpdated 1 mo ago
    Marketing & SEOAuto-check passed

  • Brief

    davepoon/buildwithclaude

    Session-start briefing from Origin. An agent skill from davepoon/buildwithclaude.

    3.6k GitHub stars~1.3k tokensUpdated yesterday
    Auto-check: notes

  • Review Brief

    every-app/open-seo

    Produce a scannable review brief for a branch or PR so the maintainer can approve without reading the whole diff.

    23k GitHub stars~1.2k tokensUpdated yesterday
    Marketing & SEOAuto-check passed

  • Traderspy Market Briefing

    sickn33/agentic-awesome-skills

    Crypto market briefing from live TraderSpy data: majors, funding, open interest, top-trader lean, fresh AI signals and screener movers.

    47k GitHub starsUsed in 1 repo~2k tokens
    Auto-check passed

  • Brief

    suboss87/FDEOps

    Clarify a new customer brief, desired outcome, constraints and evidence gaps.

    957 GitHub stars~339 tokensUpdated yesterday
    Auto-check passed

  • Case Brief

    anthropics/claude-for-legal

    Official

    Brief a case in your preferred format. An agent skill from anthropics/claude-for-legal.

    9.6k GitHub starsUsed in 3 repos~1.6k tokens
    Auto-check passed

More from aiblueprinthq/ai-blueprint

All 20 skills in this repo

  • Adopt

    aiblueprinthq/ai-blueprint

    Adopt Blueprint into an existing brownfield codebase by surveying shipped behavior and generating plans, standards, commands, adapter choices, and visibility setup.

    463 GitHub stars~2.7k tokensUpdated yesterday
    Auto-check passed

  • CI

    aiblueprinthq/ai-blueprint

    Set up or normalize one project Verify command and matching GitHub Actions checks while preserving existing CI, with an optional local pre-push hook.

    463 GitHub stars~2.2k tokensUpdated yesterday
    Auto-check passed

  • Doctor

    aiblueprinthq/ai-blueprint

    Run a Blueprint health and context check covering setup, adapters, commands, visibility, plans, overview freshness, configuration, dashboard state, and workflow drift.

    463 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check: notes

  • Feature

    aiblueprinthq/ai-blueprint

    Turn the next, named, or numbered build-plan feature into a buildable current-feature.md spec with small steps and done-when criteria.

    463 GitHub stars~2.8k tokensUpdated yesterday
    Auto-check passed

  • Onboard

    aiblueprinthq/ai-blueprint

    Onboard a fresh or early scaffold after Blueprint is overlaid by tuning commands, standards, adapters, visibility, and context loading.

    463 GitHub stars~4.5k tokensUpdated yesterday
    Auto-check passed

  • Overview

    aiblueprinthq/ai-blueprint

    Validate and normalize project-plan.md and build-plan.md, then generate the durable project-overview.md used by agents.

    463 GitHub stars~3.8k tokensUpdated yesterday
    Auto-check passed

Questions about Brief

What does Brief do?

Brief an upcoming build-plan feature without writing files. An agent skill from aiblueprinthq/ai-blueprint. Brief is an agent skill from aiblueprinthq/ai-blueprint. Brief an upcoming build-plan feature without writing files.

When should I use Brief?

Brief fits situations like: feature previews; what comes next; build-order decisions before /feature.

How do I install Brief in Claude Code?

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

How do I install Brief in Codex?

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

Can I use 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 aiblueprinthq/ai-blueprint --skill 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/brief, .gemini/skills/brief, .github/skills/brief and .opencode/skills/brief in your project.

What does Brief need to run?

SKILL.md names no scripts, command-line tools or credentials: Brief is instructions for the agent only.

Does 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 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 Brief use?

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 Brief use?

About 1.3k tokens (SKILL.md is roughly 5.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Brief?

Skills that share tags, products or a category with Brief: Brief (alirezarezvani/claude-skills, 28k stars), Brief (davepoon/buildwithclaude, 3.6k stars), Review Brief (every-app/open-seo, 23k stars) and Traderspy Market Briefing (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Brief?

aiblueprinthq (a GitHub organization) maintains it in aiblueprinthq/ai-blueprint, which has 463 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on October 8, 2026.

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