Product and code · Guides
Write acceptance criteria from a product brief
Acceptance criteria should describe observable behavior, including failure paths.
From the cub house
Blog
Practical briefs, worked examples and review checklists. Use these workflows with the tools you have connected.
-
Accounts · Checklists
Check your account recovery preparation
Recovery depends on the correct marketplace and a usable one-time code.
Research · Guides
Create an annotated bibliography from supplied sources
An annotation should describe a source's relevance and limits, not merely restate its title.
Product and code · Guides
Review API documentation for contract mismatches
API examples should match the implemented route, authentication and response shape.
Teammates and skills · Comparisons
Archive an employee or withdraw a publication?
Local employees and marketplace publications are separate records.
Operations · Guides
Create an asset inventory from a folder
An inventory should describe what files exist and what requires review, without deleting or reorganizing anything during the first pass..
Writing · Guides
Create a blog outline from your team's own notes
An original article should answer a real question using evidence or experience you can substantiate.
Product and code · Guides
Turn rough notes into a reproducible bug report
A bug report should separate observed behavior from the reporter's theory.
Product and code · Guides
Create a changelog from reviewed commits
Commit messages are clues about implementation, not a complete account of user impact.
Spreadsheets · Guides
Choose a chart that answers the business question
Start with the comparison the reader needs to make.
Presentations · Guides
Write chart-slide captions that explain the evidence
A caption should identify the comparison, period and unit before interpreting the pattern.
Research · Guides
Audit a draft's claims against its sources
A claim audit separates supported statements from unsupported additions.
Product and code · Checklists
Review a code teammate's proposed change
A code change needs evidence that it solves the stated problem without unrelated edits.
Research · Guides
Build a feature matrix from dated source material
A feature comparison needs a consistent definition and a snapshot date.
Product and code · Guides
Inventory configuration without exposing secrets
A configuration inventory should list names, purpose and where values come from.
Presentations · Guides
Apply a slide theme with a reviewable checklist
Theme cleanup should make typography, spacing and colors consistent while preserving the underlying message.
Research · Checklists
Keep examples and measured results clearly separate
Readers should be able to tell whether a number is a fixture, an estimate or an observed result.
Writing · Guides
Adapt one approved source into several useful formats
Repurposing should match each channel's reading context while keeping facts consistent.
Spreadsheets · Comparisons
CSV or XLSX for a generated data deliverable?
Choose the format from the next person's task. Compare the choices before starting your task.
Research · Guides
Code customer feedback with an explicit rubric
Feedback categories are useful when another reviewer could apply the same rules.