/skill-status

name: skill-status
description: "Show where you are in the workflow and what to do next — use for progress checks and orientation"
disable-model-invocation: true

> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex. > Cross-reference commands use installed skill names in Codex rather than `/octo:*` slash commands. > Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it. > For host tool equivalents, see `skills/blocks/codex-host-adapter.md`.

Project Status Dashboard

Overview

Display current project status, roadmap progress, blockers, and intelligent next-action suggestions based on workflow state.

**Core principle:** Read state → Display dashboard → Route intelligently.

When to Use

**Use this skill when user asks:**

• "What's the status?" or "Show me progress"
• "Where am I in the workflow?"
• "What should I do next?"
• "What's the current phase?"
• "Are there any blockers?"
• "What have I been working on?" or "Summarize recent work"
• "Update project memory" or "Update CLAUDE.md"

**Do NOT use for:**

• Creating new projects (use /octo:embrace)
• Modifying state (use octo-state.sh write_state)
• Detailed phase planning (use flow-* skills)

The Process

Phase 1: Check Project Initialization

Step 1: Verify .octo/ Directory Exists

# Check if project is initialized
if [[ ! -d ".octo" ]]; then
    echo "No project initialized"
    exit 1
fi

**If .octo/ does not exist:**

## Project Status

**Status:** Not initialized

No Claude Octopus project found in this directory.

### Get Started

Run `/octo:embrace [your project description]` to initialize a new project and start the Double Diamond workflow.

**Example:**

/octo:embrace build a user authentication system

This will:
1. Create .octo/ directory structure
2. Initialize STATE.md, PROJECT.md, ROADMAP.md
3. Begin Discover phase (research and exploration)

**Stop here** - do not proceed to Phase 2.

Phase 2: Read Current State

Step 1: Execute octo-state.sh read_state

# Read current state from STATE.md
./scripts/octo-state.sh read_state

**Expected output format:**

schema=1.0
last_updated=2026-02-02T10:30:00Z
current_phase=2
current_position=define-requirements
status=in_progress

Step 2: Parse State Variables

Extract key-value pairs:

• `current_phase` - Phase number (1-4)
• `current_position` - Specific position within phase
• `status` - Current workflow status
• `last_updated` - Last state modification timestamp

Phase 3: Read Roadmap

Step 1: Read ROADMAP.md

# Read roadmap for phase overview
cat .octo/ROADMAP.md

Step 2: Extract Phase Information

Parse ROADMAP.md to identify:

• Phase names (Discover, Define, Develop, Deliver)
• Phase descriptions
• Success criteria for each phase
• Dependencies between phases

Phase 4: Display Dashboard

Step 1: Build Status Dashboard

## Project Status

**Phase:** Phase {current_phase} - {phase_name}
**Position:** {current_position}
**Status:** {status}
**Last Updated:** {last_updated}

### Roadmap Progress

- [x] Phase 1: Discover - complete
- [ ] Phase 2: Define - in_progress  <-- YOU ARE HERE
- [ ] Phase 3: Develop - not_started
- [ ] Phase 4: Deliver - not_started

### Current Phase Details

**Phase 2: Define (Grasp)**
- **Goal:** Clarify requirements and scope
- **Position:** {current_position}
- **Status:** {status}

### Blockers

{blockers or "None"}

### Suggested Next Action

{intelligent routing based on status}

Step 2: Determine Phase Completion Status

Map `current_phase` and `status` to completion markers:

| Phase | Status | Marker | |-------|--------|--------| | 1 | complete | `[x] Phase 1: Discover - complete` | | 2 | in_progress | `[ ] Phase 2: Define - in_progress <-- YOU ARE HERE` | | 3 | not_started | `[ ] Phase 3: Develop - not_started` | | 4 | not_started | `[ ] Phase 4: Deliver - not_started` |

Phase 5: Intelligent Routing

Step 1: Map Status to Suggestion

Use this routing table:

| Status | Suggestion | |--------|-----------| | `ready` | "Run `/octo:embrace [description]` to start the workflow" | | `planning` | "Continue planning in current phase. Use `/octo:define` to refine requirements." | | `building` | "Continue implementation. Use `/octo:develop` to build features." | | `in_progress` | "Continue with current phase. Check .octo/phases/phase{N}/ for details." | | `blocked` | "Review blockers above. Use `/octo:issues` to track and resolve issues." | | `complete` | "Phase complete. Proceed to next phase or run `/octo:ship` to finalize." | | `complete_with_gaps` | "Phase complete with known gaps. Review .octo/ISSUES.md before proceeding." | | `shipped` | "Project delivered! Review .octo/LESSONS.md for retrospective." | | `paused` | "Project paused. Resume with `/octo:embrace` or check .octo/STATE.md for context." |

Step 2: Phase-Specific Routing

If `status=in_progress`, provide phase-specific guidance:

**Phase 1 (Discover):**

Continue research and exploration.
- Use `/octo:research [topic]` for multi-AI research
- Use `/octo:debate [question]` for decision support

**Phase 2 (Define):**

Continue requirements clarification.
- Use `/octo:prd` to write product requirements
- Use `/octo:define` to refine scope

**Phase 3 (Develop):**

Continue implementation.
- Use `/octo:develop` to build features
- Use `/octo:tdd` for test-driven development
- Use `/octo:review` for code quality checks

**Phase 4 (Deliver):**

Continue validation and delivery.
- Use `/octo:deliver` for final review
- Use `/octo:security` for security audit
- Use `/octo:ship` to finalize delivery

Example Outputs

Example 1: Project Not Initialized

## Project Status

**Status:** Not initialized

No Claude Octopus project found in this directory.

### Get