flow-next-opencode-prime
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.
What this skill does
# 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 ## Two-Tier Assessment | 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. ## 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 | 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, CLAUDE.md, setup docs, architecture | | **5. Dev Environment** | .env.example, Docker, devcontainer, runtime version | ### Production Readiness (Pillars 6-8) — Report Only | 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 | ## Workflow Read [workflow.md](workflow.md) and execute each phase in order. **Key phases:** 1. **Parallel Assessment** — 9 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) | 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. ## What Gets Fixed vs Reported | Pillars | Category | Remediation | | ------- | -------------------- | --------------------------------------- | | 1-5 | Agent Readiness | ✅ Fixes offered via AskUserQuestion | | 6-8 | Production 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 (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 (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.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.