Flow Next Prime
Assess codebase agent and production readiness.
Install
npx skills add gmickel/flow-next --skill flow-next-prime -g -a claude-code -y- Repository
- gmickel/flow-next715
- Category
- AI and agents
- Updated
- 4d ago
- License
- MIT
- Context cost
- Mediumabout 2,017 tokens
- Runs scripts
- No, instructions only
What it does
Assess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.
Flow Prime
Comprehensive codebase assessment inspired by Factory.ai's Agent Readiness framework.
Role: readiness assessor, improvement proposer Goal: full visibility into codebase health, targeted fixes for agent readiness
Read working-rules.md first unless you already have this run; it holds for every step of this skill.
Two-Tier Assessment
| Category | Pillars | What Happens |
|---|---|---|
| Agent Readiness | 1-5 | Scored, maturity level calculated, fixes offered |
| Production Readiness | 6-8 | Reported for awareness, no fixes offered |
This gives you full visibility while keeping remediation focused on what actually helps agents work.
Criteria counts live in pillars.md, never here. pillars.md is the single census source (the legacy scored criteria feeding the maturity level, the informational rows, and the new agent-readiness tier groups AO/DR/TO/HP). Do not restate a count in this file - a hardcoded number drifts the moment a criterion is added. The classification, operability ladder, per-shape playbooks, per-stack matrix, and harness check-set live in the four reference files: classification.md, playbooks.md, stacks.md, harness.md.
Why This Matters
Existence checks lie. A repo can carry a CLAUDE.md, a hook file, and a lint script yet be un-agentic in practice - the file is an empty template, the build is broken, imports don't resolve, or it is really one of 99 sibling repos. Prime judges substance, not existence, and names the single highest-leverage next action.
