Receber por email
← Voltar para o catálogo

brief

Generate a compiled decision brief from the current sprint's claims.

85estrelas
Atualizado há 6 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add grainulation/grainulator

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/brief-grainulation/svg)](https://www.skillteca.com.br/skills/brief-grainulation)
#ai

Skills relacionadas

Ver todas de Pesquisa e Web →

Alerta por categoria

Receba novas skills de Pesquisa e Web toda segunda

1 email curto, só com as skills novas de Pesquisa e Web. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

/brief -- Generate a decision brief

The user wants a compiled output document from the current sprint.

Arguments

$ARGUMENTS

Optional: output format (pdf, html, md). Default: html.

Instructions

  1. Run wheat_compile to ensure compilation is current and there are no blocking conflicts.
  2. If compilation fails due to unresolved conflicts, stop and suggest /resolve.
  1. Check sprint readiness via wheat_status:
  2. Minimum 5 active claims to generate a meaningful brief
  3. At least 2 topics covered
  4. Warn if all claims are the same type (type monoculture)
  1. Read compilation.json -- this is the source of truth, never read claims.json directly for output.
  1. Read the template at ${CLAUDE_PLUGIN_ROOT}/skills/_templates/sidebar-brief.html for the canonical accessible HTML structure. All generated HTML MUST follow this template exactly. Note: the path uses ${CLAUDE_PLUGIN_ROOT} because the template lives in the Grainulator plugin directory, not the user's repo.
  1. Generate the brief using mill_convert:
  2. Format: user-requested or default to HTML
  3. Structure: Executive summary, key findings by topic, risks and mitigations, recommendations, evidence appendix
  4. Include claim IDs as references throughout
  1. WCAG compliance checklist -- first read and apply every item from

${CLAUDE_PLUGIN_ROOT}/skills/_templates/wcag-shared.md, then verify these brief-specific items:

  • [ ] <nav aria-label="Table of contents"> wrapping sidebar links
  • [ ] aria-current="page" on active sidebar link (JS IntersectionObserver updates this)
  • [ ] Heading hierarchy: <h1> page title, <h2> sections, <h3> subsections -- never skip levels
  • [ ] All <table> elements have <caption> and <th scope="col|row">
  • [ ] Mobile sidebar uses <details><summary> disclosure, not display: none
  • [ ] Tags include text prefix (e.g., "Tested: verified"), never color alone
  1. Write output to output/brief.<ext> in the sprint directory.
  1. Print summary:

``` Brief generated: output/brief.<ext> Claims: <count> active, <count> topics Strongest evidence: <tier>

Next steps: /present -- turn this into a slide deck /blind-spot -- check for gaps before sharing /status -- review the full sprint dashboard ```

Compartilhar X LinkedIn