Plugins

2 plugins

@brycewang-stanford

Twelve-skill bundle covering the Science manuscript lifecycle: workflow router, scope/significance fit, advance framing, abstract + one-sentence summary, main-text writing, display items, statistics & reproducibility, data/materials/code availability, reference style, cover letter, submission preflight, and reviewer rebuttal.

2 skills · plugin

@brycewang-stanford

Twelve-skill bundle covering the Cell manuscript lifecycle: workflow router, scope/significance fit, single-narrative framing, the Highlights + eTOC + Graphical Abstract trio, the ≤150-word Summary, main-text writing, display items, STAR Methods + Key Resources Table, data/code availability, Cell Press author–date references, submission preflight + cover letter, and reviewer rebuttal.

9 skills · plugin

Results for “cover-letter”

1 skill

Create OR review a page-brief — the artifact BETWEEN a wireflow and the full PRD. It turns each unique page/screen of a product into documented requirements TIED TO JOBS: a self-contained board card per page (what the page is accountable for, the job-tagged checklist of what it must let you do, the journeys it appears in, what it connects to, and the acceptance criteria that say how you'd know it's right). It is the "PRD per page", not a sitemap — and it stops ABOVE the screen: no components, no layout, no hierarchy. Use whenever the user wants to "spec the pages", "document each screen", turn a wireflow + live design into per-page requirements, or asks "what does this page need to do / which jobs pass through it" — even if they never say "page-brief". Natural NEXT STEP after the wireflow skill. ALSO use it to REVIEW an existing page-brief / screen catalog. In the A-Team pipeline this is a definition-phase skill: output lands in docs/features/<slug>/briefs/pages/, job codes are the durable [[NN]] ids from doc