Capability Report Refresh Implementation Plan

For Claude: REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.

Goal: Update docs/workdocs/capability-report.md to reflect the current codebase state with evidence-backed references.

Architecture: This is a documentation-only change. We will inventory current capabilities by reading source files, generators, and justfile recipes, then update the report sections to match verified evidence and remove stale claims.

Tech Stack: Markdown docs, shell commands (rg, ls, sed), and repo sources.

Task 1: Inventory current capability evidence

Files:

• Modify: docs/workdocs/capability-report.md
• Reference: .github/copilot-instructions.md
• Reference: ARCHITECTURE.md
• Reference: PRODUCT.md
• Reference: AGENTS.md
• Reference: SKILLS.md
• Reference: docs/workdocs/project_state.md
• Reference: justfile
• Reference: tools/, generators/, apps/, services/, libs/

Step 1: Read baseline documentation

Run:

1
sed -n '1,240p' docs/workdocs/capability-report.md

Expected: current report sections and claims.

Step 2: Re-scan key status docs

Run:

1
sed -n '1,240p' docs/workdocs/project_state.md

Expected: current completion percentages and gaps list.

Step 3: Enumerate pipeline and validator tooling

Run:

1
rg --files -g 'tools/*.py'

Expected: list of Python tools for validation/compilation.

Step 4: Enumerate generators and templates

Run:

1
rg --files generators tools/codegen/templates

Expected: list of generators and templates for codegen claims.

Step 5: Enumerate services and adapters

Run:

1
ls -1 services

Expected: current services list for report.

Step 6: Capture CLI commands

Run:

1
rg -n "\bcommand\b|commands" apps/sea-forge-cli/src/commands

Expected: list of CLI command modules.

Step 7: Confirm workflow recipes

Run:

1
rg -n "^just " justfile

Expected: current workflow commands.

Task 2: Update capability report with verified evidence

Files:

• Modify: docs/workdocs/capability-report.md

Step 1: Update metadata

Edit:

• Update Date to 2026-01-28
• Update Version Analyzed to current repo version (if defined in docs or tags; otherwise mark as unreleased)

Step 2: Refresh capabilities and evidence

Edit sections to match current evidence:

• Core capabilities tables (tools, validators, pipeline stages)
• Services list
• AI/Agent integration hooks
• Supported workflows (justfile commands)
• Guardrails and enforcement
• Drift/misalignment handling
• Not implemented list
• Evidence-backed capability list
• Notes for documentation accuracy
• Skeptical engineer assessment

Step 3: Remove or revise stale claims

Remove any claims that cannot be corroborated by code or docs. If evidence is ambiguous, mark as unknown and add a short note.

Step 4: Add new evidence

Add any newly discovered capabilities (e.g., additional services, generators, adapters, or validation steps) with file-path citations.

Task 3: Consistency review

Files:

• Modify: docs/workdocs/capability-report.md

Step 1: Cross-check references

Ensure every major claim cites a file path or script where evidence exists.

Step 2: Ensure formatting consistency

Run:

1
rg -n "^#+ " docs/workdocs/capability-report.md

Expected: consistent heading structure; no orphan sections.

Step 3: Final read-through

Run:

1
sed -n '1,240p' docs/workdocs/capability-report.md

Expected: accurate, up-to-date narrative and tables.

Step 4: Optional lint

If you want a broader check:

1
just ci-quick

Expected: pass (lint + specs). Not required for doc-only changes.