skill status

Engineering Community

Skill notes

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?"

Phase 1: Check Project Initialization

Step 1: Verify .octo/ Directory Exists If .octo/ does not exist: /octo:embrace build a user authentication system Stop here - do not proceed to Phase 2.

Phase 2: Read Current State

Step 1: Execute octo-state.sh read_state Expected output format: Step 2: Parse State Variables Extract key-value pairs: current_phase - Phase number (1-4)

Phase 3: Read Roadmap

Step 1: Read ROADMAP.md Step 2: Extract Phase Information Parse ROADMAP.md to identify: Phase names (Discover, Define, Develop, Deliver) Phase descriptions

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@nyldn · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Phase 1: Check Project Initialization

Step 1: Verify .octo/ Directory Exists If .octo/ does not exist: /octo:embrace build a user authentication system Stop here - do not proceed to Phase 2.

02
Phase 2: Read Current State

Step 1: Execute octo-state.sh read_state Expected output format: Step 2: Parse State Variables Extract key-value pairs: `current_phase` - Phase number (1-4)

03
Phase 3: Read Roadmap

Step 1: Read ROADMAP.md Step 2: Extract Phase Information Parse ROADMAP.md to identify: Phase names (Discover, Define, Develop, Deliver) Phase descriptions

04
Phase 4: Display Dashboard

Step 1: Build Status Dashboard Step 2: Determine Phase Completion Status Map `current_phase` and `status` to completion markers: Phase · Status · Marker 1 · complete · `[x] Phase 1: Discover - complete`

05
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."

06
Phase 6: Recent Activity Summary (Cross-Session)

When the user asks "what have I been working on", "summarize recent work", or "update project memory", generate a cross-session activity summary. Step 1: Gather Recent Activity Step 2: Summarize Activity Build a concise summary grouped by theme: Step 3: Suggest CLAUDE.md Updates

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.