Skip to content
Back to skills

Brief Writer

ASecurity

Finishes a Fetchproof project's handoff - drafts research/BRIEF.md with brief.mjs, answers the two sections the corpus cannot fill (Contradictions, Decision with a concrete first build step and what is out of scope), and declares the review with "Reviewed by: agent". Use on a collector once preflight prints PASS, when brief.mjs --state says draft, or when the user asks for the brief or the handoff.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 22, 2026
ai-agentsrustnodegit

Security analysis

A100/100

Scanned October 22, 2026

npx -y skills add StepenkoAnatoli/Fetchproof --skill brief-writer --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Brief Writer?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Brief Writer
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/stepenkoanatoli-brief-writer/badge)](https://www.skillsdirectory.com/skills/stepenkoanatoli-brief-writer)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: brief-writer
description: Finishes a Fetchproof project's handoff - drafts research/BRIEF.md with brief.mjs, answers the two sections the corpus cannot fill (Contradictions, Decision with a concrete first build step and what is out of scope), and declares the review with "Reviewed by: agent". Use on a collector once preflight prints PASS, when brief.mjs --state says draft, or when the user asks for the brief or the handoff.
---

# Brief writer

The brief is phase 1's deliverable and the only file phase 2 is required to read.

## Steps

1. `node "$HOME/.agents/fetchproof/bin/preflight.mjs"` - PASS first. The brief records
   the gate state and its warnings; it does not hide them.
2. `node "$HOME/.agents/fetchproof/bin/brief.mjs"` - drafts it from the corpus: intent,
   verified claims with sources, known unknowns with their day-one steps.
3. Answer the two **TODO** sections:
   - **Contradictions and how they were resolved** - both sides, which is trusted and
     why, and whether corroboration was independent (`source-grader`). If there were
     none, say what was compared.
   - **Decision** - what to build first, concretely enough to start from this file
     alone, and what is explicitly out of scope.
4. Replace the `Reviewed by:` placeholder with `Reviewed by: agent` - a declaration of who
   did the review steps (ADR-0074, ADR-0107).
5. `node "$HOME/.agents/fetchproof/bin/brief.mjs" --state` - `authored`.
6. `node "$HOME/.agents/fetchproof/bin/handoff.mjs"` - exit 0 - then commit the corpus
   **with** `research/raw/.fetches.jsonl` (`git add -f` it by name if a dotfile rule hides it).

## Rules

- Re-running `brief.mjs` after an edit refuses without `--force`; `--force` keeps the old
  one as `BRIEF.md.bak-<date>`.
- A claim not in `research/EVIDENCE.md` does not enter the brief.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.