Loading source
Pulling the file list, source metadata, and syntax-aware rendering for this listing.
Source from bundle
Facilitate a Value Management style interrogation of a plan, design, problem, or product decision. Use when the user wants a deeper successor to grill-me - on
Files
Skill
Size
Entrypoint
Format
Open file
Syntax-highlighted preview of this file as included in the skill package.
references/function-analysis.md
1# Function Analysis23Functions describe **what something does**, not how. Phrasing matters: it forces the team out of solution language.45## Rules67- **Verb + noun.** Active verb, measurable noun. "Notify operator", not "notification system".8- **One function per line.** Compound verbs hide design choices.9- **No brand or implementation in the noun.** "Persist verdict" not "Write Postgres row".10- **Quantify when possible.** "Bound spend <= $X/day".1112## Classification1314- **Basic function** - the reason the thing exists. Removing it kills the value.15- **Secondary function** - supports, enables, protects, or pleases. Removable if a better path exists.16- **Unnecessary function** - historical, habitual, performative. First candidate for cut.17- **Required function** - imposed by law, contract, or policy. Cannot be cut without authority.1819Mark each function with one tag.2021## FAST diagram quickstart2223Function Analysis System Technique. Read left to right: higher-order *why* on the left, lower-order *how* on the right. For each function, ask:2425- **Why does this function exist?** -> answer is the function to its left.26- **How is it achieved?** -> answers are the functions to its right.27- **When else?** -> concurrent functions sit vertically.2829Stop expanding when you reach functions whose answer is "by implementation". That column is the design boundary.3031A skinny FAST is enough for most software work. Three columns: outcome -> primary functions -> supporting functions.3233## Examples3435### Software - antispam verdict pipeline36- Basic: *Decide verdict* (allow|block|unclear).37- Basic: *Persist verdict* (auditable, queryable).38- Basic: *Bound spend* on LLM calls.39- Secondary: *Explain verdict* to moderator.40- Secondary: *Cache verdict* for repeat content.41- Unnecessary: *Visualize verdict graph in admin UI* - historical, no decisions taken from it.42- Required: *Retain logs >= 30 days* (policy).4344### Non-software - quarterly offsite45- Basic: *Align direction* across leads.46- Basic: *Surface conflict* safely.47- Secondary: *Reward team*.48- Secondary: *Onboard new hires*.49- Unnecessary: *Produce slide deck* - nobody re-reads it.50- Required: *Stay within travel budget*.5152## Drill question5354Ask the user, one at a time, with *Recommended:* attached:5556> "If we removed function X, what concretely fails?" - *Recommended: check if anything downstream (code, runbook, contract, user flow) actually depends on X; if no dependency surfaces from inspection, treat X as a tentative cut candidate and ask the user to confirm.*5758Cut what survives this question. Promote what doesn't.59