From code-forge
Displays a feature dashboard with task-level progress from state.json, or detailed status for a specific feature. Useful for checking progress and viewing what's left.
How this skill is triggered — by the user, by Claude, or both
Slash command
/code-forge:statusThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
@../shared/execution-entrypoint.md
@../shared/execution-entrypoint.md
For this skill: start at the first executable step. If you catch yourself about to say "falling back to manual status check", STOP and go to the indicated step.
Display a dashboard of all features or detailed progress for a specific feature.
/code-forge:status # Show project dashboard
/code-forge:status user-auth # Show detail for one feature
Load Config → Scan Features → Display Dashboard or Detail → Update Overview
@../shared/configuration.md
Based on arguments:
Run the status renderer — it scans both plan locations, recomputes progress from
each state.json, and prints the ready-to-display table so the raw state files
never enter context. Resolve <cf_scripts> once (see Locating the script
layer in the configuration step), then:
python3 "<cf_scripts>/cf-status.py" [--output-dir "<output_dir>"]
Print its output as the dashboard, then continue to 2.3 (update overview) and
2.4 (handle selection). If python3 is unavailable or the script is missing,
build the table by hand using 2.1–2.2 below.
<base_dir>/<output_dir>/state.json files in both locations:
<output_dir>/*/state.json (standard plans).code-forge/tmp/*/state.json (temporary plans created with --tmp)state.json, extract: feature, status, progress.*, metadata.source_doc, updated.code-forge/tmp/ with [tmp] suffix in displayFeatures found: Show table with #, Feature, Progress, Status, Last Updated.
code-forge — Feature Dashboard
# | Feature | Progress | Status | Last Updated
1 | user-auth | 3/5 (60%) | in_progress | 2026-02-14
2 | file-upload | 0/3 (0%) | pending | 2026-02-13
3 | notifications | 4/4 (100%) | completed | 2026-02-12
Commands:
/code-forge:plan @doc.md Create new plan from document
/code-forge:plan "requirement" Create new plan from prompt
/code-forge:impl <feature> Execute tasks for a feature
/code-forge:status <feature> View feature detail
/code-forge:fix "description" Debug a bug
/code-forge:review <feature> Review completed feature
Offer actions via AskUserQuestion:
No features found: Show empty state with instructions:
{base_dir}/{input_dir}/{feature-name}.md/code-forge:plan @path/to/feature.md or /code-forge:plan "requirement text"After scanning, regenerate {output_dir}/overview.md using Step 4 logic.
/code-forge:plan commandFast path: python3 "<cf_scripts>/cf-status.py" <feature_name> locates the
feature (output dir, then .code-forge/tmp/), recomputes progress, and prints
the detail table directly — use it and skip to Step 4. On a missing feature it
exits non-zero with an error listing where it looked. Fall back to the manual
steps below if python3 is unavailable.
{output_dir}/{feature_name}/state.json.code-forge/tmp/{feature_name}/state.jsonRead state.json and display:
code-forge — Feature: user-auth
Status: in_progress
Source: docs/features/user-auth.md
Created: 2026-02-10
Updated: 2026-02-14
Tasks:
# | Task | Status | Started | Completed
1 | setup | completed | 2026-02-10 | 2026-02-10
2 | models | completed | 2026-02-11 | 2026-02-11
3 | auth-logic | in_progress | 2026-02-14 | —
4 | api-endpoints | pending | — | —
5 | integration | pending | — | —
Progress: 2/5 (40%)
Commands:
/code-forge:impl user-auth Continue execution
/code-forge:review user-auth Review completed tasks
/code-forge:fix "..." Fix a bug in this feature
@../shared/overview-generation.md
Display: Project overview updated: {output_dir}/overview.md
npx claudepluginhub tercel/tercel-claude-plugins --plugin code-forgeGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.