菜单
Use when assessing codebase readiness for agents or production. Triggers on /flow-code:prime, 'assess this codebase', or 'is this repo ready'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Internal pipeline engine. Manages the entire pipeline (brainstorm, plan, plan-review, work, impl-review, close) via flowctl phase commands. Invoked by /flow-code:go.
Use when exploring requirements before planning. Pressure-tests ideas, generates approaches, and outputs a requirements doc for /flow-code:plan. Supports --auto mode for AI self-interview (no human input needed).
Use when exploring requirements before planning. Pressure-tests ideas, generates approaches, and outputs a requirements doc for /flow-code:plan.
Use when planning features or designing implementation. Triggers on /flow-code:plan with text descriptions or Flow IDs.
Use when reviewing code changes — self-review in Worker Phase 6, impl-review, or PR review. Applies five-axis scoring with severity labels.
Use when implementing a plan or working through a spec. Triggers on /flow-code:work with Flow IDs.
| name | flow-code-prime |
| description | Use when assessing codebase readiness for agents or production. Triggers on /flow-code:prime, 'assess this codebase', or 'is this repo ready'. |
| tier | 2 |
| user-invocable | false |
| context | fork |
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
| Category | Pillars | What Happens |
|---|---|---|
| Agent Readiness | 1-5 (30 criteria) | Scored, maturity level calculated, fixes offered |
| Production Readiness | 6-8 (18 criteria) | Reported for awareness, no fixes offered |
This gives you full visibility while keeping remediation focused on what actually helps agents work.
Agents waste cycles when:
These are environment problems, not agent problems. Prime helps fix them.
Full request: $ARGUMENTS
Accepts:
--report-only or report only (skip remediation, just show report)--fix-all or fix all (apply all agent readiness fixes without asking)Examples:
/flow-code:prime/flow-code:prime --report-only/flow-code:prime ~/other-project| Pillar | What It Checks |
|---|---|
| 1. Style & Validation | Linters, formatters, type checking, pre-commit hooks |
| 2. Build System | Build tools, commands, lock files, monorepo tooling |
| 3. Testing | Test framework, commands, coverage, verification |
| 4. Documentation | README, AGENTS.md, setup docs, architecture |
| 5. Dev Environment | .env.example, Docker, devcontainer, runtime version |
| Pillar | What It Checks |
|---|---|
| 6. Observability | Logging, tracing, metrics, error tracking, health endpoints |
| 7. Security | Branch protection, secret scanning, CODEOWNERS, Dependabot |
| 8. Workflow & Process | CI/CD, PR templates, issue templates, release automation |
Read workflow.md and execute each phase in order.
Key phases:
| Level | Name | Description | Score |
|---|---|---|---|
| 1 | Minimal | Basic project structure only | <30% |
| 2 | Functional | Can build and run, limited docs | 30-49% |
| 3 | Standardized | Agent-ready for routine work | 50-69% |
| 4 | Optimized | Fast feedback loops, comprehensive docs | 70-84% |
| 5 | Autonomous | Full autonomous operation capable | 85%+ |
Level 3 is the target for most teams. Don't over-engineer.
| Pillars | Category | Remediation |
|---|---|---|
| 1-5 | Agent Readiness | ✅ Fixes offered via AskUserQuestion |
| 6-8 | Production Readiness | ❌ Reported only, address independently |
tooling-scout — linters, formatters, pre-commit, type checkingagents-md-scout — AGENTS.md/AGENTS.md analysisenv-scout — environment setuptesting-scout — test infrastructurebuild-scout — build systemdocs-gap-scout — README, ADRs, architectureobservability-scout — logging, tracing, metrics, healthsecurity-scout — GitHub settings, CODEOWNERS, secretsworkflow-scout — CI/CD, templates, automationAll 9 scouts run in parallel for speed.