flow-next-prime

0
0
Source

Comprehensive codebase assessment for agent and production readiness. Scans 8 pillars (48 criteria), verifies commands work, checks GitHub settings. Reports everything, fixes agent readiness only. Triggers on /flow-next:prime.

Install

mkdir -p .claude/skills/flow-next-prime && curl -L -o skill.zip "https://mcp.directory/api/skills/download/8799" && unzip -o skill.zip -d .claude/skills/flow-next-prime && rm skill.zip

Installs to .claude/skills/flow-next-prime

About this skill

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

Two-Tier Assessment

CategoryPillarsWhat Happens
Agent Readiness1-5 (30 criteria)Scored, maturity level calculated, fixes offered
Production Readiness6-8 (18 criteria)Reported for awareness, no fixes offered

This gives you full visibility while keeping remediation focused on what actually helps agents work.

Why This Matters

Agents waste cycles when:

  • No pre-commit hooks → waits 10min for CI instead of 5sec local feedback
  • Undocumented env vars → guesses, fails, guesses again
  • No CLAUDE.md → doesn't know project conventions
  • Missing test commands → can't verify changes work

These are environment problems, not agent problems. Prime helps fix them.

Input

Full request: $ARGUMENTS

Accepts:

  • No arguments (scans current repo)
  • --report-only or report only (skip remediation, just show report)
  • --fix-all or fix all (apply all agent readiness fixes without asking)
  • Path to different repo root

Examples:

  • /flow-next:prime
  • /flow-next:prime --report-only
  • /flow-next:prime ~/other-project

The Eight Pillars

Agent Readiness (Pillars 1-5) — Fixes Offered

PillarWhat It Checks
1. Style & ValidationLinters, formatters, type checking, pre-commit hooks
2. Build SystemBuild tools, commands, lock files, monorepo tooling
3. TestingTest framework, commands, coverage, verification
4. DocumentationREADME, CLAUDE.md, setup docs, architecture
5. Dev Environment.env.example, Docker, devcontainer, runtime version

Production Readiness (Pillars 6-8) — Report Only

PillarWhat It Checks
6. ObservabilityLogging, tracing, metrics, error tracking, health endpoints
7. SecurityBranch protection, secret scanning, CODEOWNERS, Dependabot
8. Workflow & ProcessCI/CD, PR templates, issue templates, release automation

Workflow

Read workflow.md and execute each phase in order.

Key phases:

  1. Parallel Assessment — 9 haiku scouts run in parallel (~15-20 seconds)
  2. Verification — Verify test commands actually work
  3. Score & Synthesize — Calculate scores, determine maturity level
  4. Present Report — Full report with all 8 pillars
  5. Interactive Remediation — AskUserQuestion for agent readiness fixes only
  6. Apply Fixes — Create/modify files based on selections
  7. Summary — Show what was changed

Maturity Levels (Agent Readiness)

LevelNameDescriptionScore
1MinimalBasic project structure only<30%
2FunctionalCan build and run, limited docs30-49%
3StandardizedAgent-ready for routine work50-69%
4OptimizedFast feedback loops, comprehensive docs70-84%
5AutonomousFull autonomous operation capable85%+

Level 3 is the target for most teams. Don't over-engineer.

What Gets Fixed vs Reported

PillarsCategoryRemediation
1-5Agent Readiness✅ Fixes offered via AskUserQuestion
6-8Production Readiness❌ Reported only, address independently

Guardrails

General

  • Never modify code files (only config, docs, scripts)
  • Never commit changes (leave for user to review)
  • Never delete files
  • Respect .gitignore patterns

User Consent

  • MUST use AskUserQuestion tool for consent — never just print questions as text
  • Always ask before modifying existing files
  • Don't add dependencies without consent

Scope Control

  • Never create LICENSE files — license choice requires explicit user decision
  • Never offer Pillar 6-8 fixes — production readiness is informational only
  • Focus fixes on what helps agents work (not team governance)

Scouts

Agent Readiness (haiku, fast)

  • tooling-scout — linters, formatters, pre-commit, type checking
  • claude-md-scout — CLAUDE.md/AGENTS.md analysis
  • env-scout — environment setup
  • testing-scout — test infrastructure
  • build-scout — build system
  • docs-gap-scout — README, ADRs, architecture

Production Readiness (haiku, fast)

  • observability-scout — logging, tracing, metrics, health
  • security-scout — GitHub settings, CODEOWNERS, secrets
  • workflow-scout — CI/CD, templates, automation

All 9 scouts run in parallel for speed.

worktree-kit

gmickel

Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.

272

flow-plan-review

gmickel

Carmack-level plan review via rp-cli context builder + chat. Use when reviewing implementation plans, architecture docs, or design specs. Triggers on mentions of plan review, design review, or architecture review.

21

flow-work

gmickel

Execute a plan file or Beads epic systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan, working through a spec, following documented steps, or executing a Beads issue ID (e.g., bd-123, gno-45, app-12).

21

flow-interview

gmickel

Interview user in-depth about a spec, bead, or feature idea to extract complete implementation details. Use when user wants to flesh out a spec, refine requirements, discuss technical details, clarify a feature before building, or asks to be interviewed about their idea. Triggers on "interview me", "ask me questions about", "flesh out this spec", "refine requirements", "help me think through".

71

flow-next-setup

gmickel

Optional local install of flowctl CLI and CLAUDE.md/AGENTS.md instructions. Use when user runs /flow-next:setup.

41

flow-next-work

gmickel

Execute a Flow epic or task systematically with git setup, task tracking, quality checks, and commit workflow. Use when implementing a plan or working through a spec. Triggers on /flow-next:work with Flow IDs (fn-1-add-oauth, fn-1-add-oauth.2, or legacy fn-1, fn-1.2, fn-1-xxx, fn-1-xxx.2).

11

You might also like

flutter-development

aj-geddes

Build beautiful cross-platform mobile apps with Flutter and Dart. Covers widgets, state management with Provider/BLoC, navigation, API integration, and material design.

1,4071,302

drawio-diagrams-enhanced

jgtolentino

Create professional draw.io (diagrams.net) diagrams in XML format (.drawio files) with integrated PMP/PMBOK methodologies, extensive visual asset libraries, and industry-standard professional templates. Use this skill when users ask to create flowcharts, swimlane diagrams, cross-functional flowcharts, org charts, network diagrams, UML diagrams, BPMN, project management diagrams (WBS, Gantt, PERT, RACI), risk matrices, stakeholder maps, or any other visual diagram in draw.io format. This skill includes access to custom shape libraries for icons, clipart, and professional symbols.

1,2201,024

ui-ux-pro-max

nextlevelbuilder

"UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient."

9001,013

godot

bfollington

This skill should be used when working on Godot Engine projects. It provides specialized knowledge of Godot's file formats (.gd, .tscn, .tres), architecture patterns (component-based, signal-driven, resource-based), common pitfalls, validation tools, code templates, and CLI workflows. The `godot` command is available for running the game, validating scripts, importing resources, and exporting builds. Use this skill for tasks involving Godot game development, debugging scene/resource files, implementing game systems, or creating new Godot components.

958658

nano-banana-pro

garg-aayush

Generate and edit images using Google's Nano Banana Pro (Gemini 3 Pro Image) API. Use when the user asks to generate, create, edit, modify, change, alter, or update images. Also use when user references an existing image file and asks to modify it in any way (e.g., "modify this image", "change the background", "replace X with Y"). Supports both text-to-image generation and image-to-image editing with configurable resolution (1K default, 2K, or 4K for high resolution). DO NOT read the image file first - use this skill directly with the --input-image parameter.

970608

pdf-to-markdown

aliceisjustplaying

Convert entire PDF documents to clean, structured Markdown for full context loading. Use this skill when the user wants to extract ALL text from a PDF into context (not grep/search), when discussing or analyzing PDF content in full, when the user mentions "load the whole PDF", "bring the PDF into context", "read the entire PDF", or when partial extraction/grepping would miss important context. This is the preferred method for PDF text extraction over page-by-page or grep approaches.

1,033496

Stay ahead of the MCP ecosystem

Get weekly updates on new skills and servers.