npx claudepluginhub mikeparcewski/wicked-garden --plugin wicked-gardencrew/# /wicked-garden:crew:status Display the current project state and available integrations. > **Scope**: `crew:status` is a **read-only state view** — no phase changes, no writes. > To **enter the post-delivery operate phase**, use `/wicked-garden:crew:operate`. > If the output is hard to parse, pipe it through `/wicked-garden:crew:explain`. ## Instructions ### 1. Find Active Project If no active project found (`"project": null`), inform user and suggest `/wicked-garden:crew:start`. ### 2. Read Project State Use the project name from the find-active result: This returns: name, cu...
/statusDisplay Conductor project status including overall progress, active tracks summary, and next actions. Optional [track-id] [--detailed] for per-track task details and blockers.
/statusDisplays compact planning status from task_plan.md: current phase and progress, phase list with icons, error count, and planning file checks.
/statusShows active and recent Codex jobs for this repository in a compact Markdown table, including review-gate status. Pass job ID for full details; supports --wait, --timeout-ms, --all.
/statusDisplays current design system state from .interface-design/system.md including direction, foundation, depth, tokens, patterns, and last updated time. Suggests setup options if no system found.
/statusDisplays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.
/statusDisplays status of tasks in the orchestration system, including summaries, distributions, detailed views, timelines, and velocity reports with filters for date, status, agent, priority, and type.
Display the current project state and available integrations.
Scope:
crew:statusis a read-only state view — no phase changes, no writes. To enter the post-delivery operate phase, use/wicked-garden:crew:operate. If the output is hard to parse, pipe it through/wicked-garden:crew:explain.
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/crew/crew.py find-active --json
If no active project found ("project": null), inform user and suggest /wicked-garden:crew:start.
Use the project name from the find-active result:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/_run.py" scripts/crew/phase_manager.py {name} status --json
This returns: name, current_phase, phase_plan, phase statuses, signals, complexity, and review_tier.
Check which plugins are installed:
# Check for wicked-brain (required companion plugin)
if curl -s --connect-timeout 1 -X POST http://localhost:4242/api -H "Content-Type: application/json" -d '{"action":"health"}' 2>/dev/null | grep -q '"ok"'; then
echo "wicked-brain: available"
else
echo "wicked-brain: not running"
fi
done
Based on available plugins:
## wicked-garden:crew Project Status
**Project**: {name}
**Phase**: {current_phase}
**Status**: {status}
**Complexity**: {complexity}/7 (review tier: {review_tier})
### Phase Progress
| Phase | Status | Notes |
|-------|--------|-------|
| clarify | {status} | {notes} |
| design | {status} | {notes} |
| qe | {status} | {notes} |
| build | {status} | {notes} |
| review | {status} | {notes} |
### Available Integrations (Level {n})
| Plugin | Status | Used In |
|--------|--------|---------|
| jam | built-in | clarify |
| search | built-in | design |
| product | built-in | qe, review |
| mem | built-in | all phases |
| wicked-brain | {running/not running} | context assembly |
### Next Steps
{Based on current phase and status}
If the current phase is "operate" or if operate data exists in the project state, show a summary:
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" -c "
import json, sys
from pathlib import Path
sys.path.insert(0, str(Path('${CLAUDE_PLUGIN_ROOT}/scripts')))
from _domain_store import DomainStore
ds = DomainStore('wicked-crew')
incidents = [i for i in ds.list('incidents') if i.get('project_id') == '{project_name}']
feedback = [f for f in ds.list('feedback') if f.get('project_id') == '{project_name}']
print(json.dumps({'incidents': len(incidents), 'feedback': len(feedback)}, indent=2))
"
If incidents or feedback exist, display:
### Operate Phase Data
| Metric | Count |
|--------|-------|
| Incidents | {incident_count} |
| Feedback | {feedback_count} |
| Checklist items | {completed}/{total} |
Use `/wicked-garden:crew:operate --status` for full operational details.
Run drift classification against the project's timeline. If the project has fewer than 5 sessions, skip this block quietly.
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" "${CLAUDE_PLUGIN_ROOT}/scripts/delivery/drift.py" classify {project_name}
When the output's classification.zone is "insufficient", skip the block
entirely (not enough history yet).
Otherwise display:
### Quality Trend (cross-session)
- **Metric**: gate_pass_rate
- **Latest**: {classification.latest}
- **Baseline mean** (last 4 sessions): {classification.baseline.mean} ± {classification.baseline.stddev}
- **Drop vs baseline**: {classification.drop_pct * 100:.1f}%
- **EWMA slope**: {classification.ewma_slope}
- **Classification**: {classification.zone} — {"SIGNAL (special-cause)" if zone == "special-cause" else "watch" if zone == "warn" else "noise (common-cause)"}
- **Sessions observed**: {classification.session_count}
{If classification.drift is true: show "Drift detected — see `wicked.quality.drift_detected` event on wicked-bus" and list `classification.reasons`}
{If actionable: recommend crew retro or gate-review; otherwise explicitly label as common-cause noise and state "no new gate will be added for common-cause variation"}
Rationale: per Issue #443 acceptance, common-cause variation must not trigger new process gates. Special-cause classification (outside 3σ) or a >=15% drop are the only signals worth escalating.
Additive section — surfaces per-artifact convergence state. The script is fail-open: it returns an empty status dict when no convergence log exists, so this section stays silent for projects that have not started tracking.
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" \
"${CLAUDE_PLUGIN_ROOT}/scripts/crew/convergence.py" status \
--project "$PROJECT" 2>/dev/null || true
sh "${CLAUDE_PLUGIN_ROOT}/scripts/_python.sh" \
"${CLAUDE_PLUGIN_ROOT}/scripts/crew/convergence.py" stall \
--project "$PROJECT" 2>/dev/null || true
If the status response has total > 0, render an additive section AFTER the
existing Phase Progress table (do not restructure the existing output):
### Convergence Lifecycle
| Artifact | State | Sessions in state | Over budget? | Last phase |
|----------|-------|-------------------|--------------|------------|
| {id} | {state} | {n} | {yes/no} | {phase} |
**Stalls** ({count}):
- {artifact}: stuck in {state} for {n} sessions
See `/wicked-garden:crew:convergence` for the raw lifecycle view and
`convergence verify-gate` for the review-phase gate verdict.
If the convergence log does not exist (empty output or total == 0), skip
this section entirely — no noise on projects that do not use convergence
tracking yet.
Based on current state:
/wicked-garden:crew:approve {phase}/wicked-garden:crew:execute/wicked-garden:crew:incident, /wicked-garden:crew:feedback, or /wicked-garden:crew:retro/wicked-garden:crew:convergence stall for the full view