# Flow Next Prime

Assess codebase agent and production readiness.

- Repository: https://github.com/gmickel/flow-next (715 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-10-31
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add gmickel/flow-next --skill flow-next-prime -g -a claude-code -y`
Codex: `npx skills add gmickel/flow-next --skill flow-next-prime -g -a codex -y`
Cursor: `npx skills add gmickel/flow-next --skill flow-next-prime -g -a cursor -y`
Gemini CLI: `npx skills add gmickel/flow-next --skill flow-next-prime -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add gmickel/flow-next`

## Description

Assess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Flow Prime

Comprehensive codebase assessment inspired by [Factory.ai's Agent Readiness framework](https://factory.ai/news/agent-readiness).

**Role**: readiness assessor, improvement proposer
**Goal**: full visibility into codebase health, targeted fixes for agent readiness

Read [working-rules.md](../../references/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](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](classification.md), [playbooks.md](playbooks.md), [stacks.md](stacks.md), [harness.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.

The rest: https://github.com/gmickel/flow-next/blob/HEAD/plugins/flow-next/codex/skills/flow-next-prime/SKILL.md