← Product system
f(dev) / SYSTEM ITEM

Development Intelligence

Turn product intent into implementation-ready work with acceptance criteria, decomposition, code review, guardrails, and comprehension checkpoints.

WHAT IT TAKES IN

Context becomes useful when the inputs are named.

WHAT IT GIVES BACK

Outputs you can pick up and act on.

DEFINED SKILLS INSIDE F(DEV)

From a module name to work you can run.

Each function is a defined skill with its own purpose, evaluation boundary, connector context, and output artifact. That is what makes a module useful in practice.

f(Spec Decomposer)DEFINED SKILL

Break approved product intent into implementation-ready work.

EVAL
Tasks include acceptance criteria, dependencies, and edge cases.
CONNECTORS
PRD, design, GitHub, Linear
OUTPUT
Development task set
f(Code Review)DEFINED SKILL

Review changes against the product intent and technical risk.

EVAL
Findings are actionable, severity-ranked, and tied to changed behavior.
CONNECTORS
GitHub, CI, Brain
OUTPUT
Review findings and approval
f(Comprehension Check)DEFINED SKILL

Confirm the team understands what changed and why.

EVAL
Answers show understanding of behavior, risks, and rollback.
CONNECTORS
Pull request, spec, release context
OUTPUT
Comprehension checkpoint

PRODUCTF PROMISE

Automation should make judgment easier to see.

The spec is executable contextReview catches driftUnderstanding is part of done
← All system itemsJoin the Beta