context-status

Answer manager questions about project status from state.md and journal.md.

4|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/leocosta/octopus --skill context-status-leocosta
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: context-status
Source: https://github.com/leocosta/octopus/tree/main/skills/context-status
Command: npx skills add https://github.com/leocosta/octopus --skill context-status-leocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reads and answers manager questions about the current workspace context by querying the materialized state in a strictly read-only manner, ensuring every claim has provenance from recorded sources.

Core Features & Use Cases

  • Read from the workspace configuration and the materialized state (state.md, journal.md) to produce grounded answers with cited sources.
  • Resolve ambiguity by showing what is known and asking for correction, avoiding guesses.
  • Provide a guided consult pathway for managers to understand status, blockers, owners, decisions, and political risk across contexts and projects.

Quick Start

Ask a natural-language question about a context or project, for example '/octopus:context-status payments', to get a grounded, read-only answer.

Frequently Asked Questions about context-status

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I get grounded answers about project status without modifying workspace data?

To get grounded answers about project status without modifying data, use a read-only consult pathway that queries the materialized state. It reads state.md and journal.md to derive provenance, ensuring every claim has cited sources without writing any data.

What is the best way to track blockers and owners across multiple project contexts?

Tracking blockers and owners across contexts requires querying the materialized state for a grounded view. By reading state.md and journal.md, you can resolve manager inquiries about ownership and political risk using strictly recorded provenance.

How do I answer natural-language questions about workspace decisions and system maps?

Answering natural-language questions about workspace decisions involves querying the materialized state directly. The system reads state.md and journal.md to provide a guided consult pathway, showing what is known and asking for correction to avoid guesses.

Does the context-status consult pathway work when project information is not fully recorded?

The consult pathway does not guess when project information is not recorded. It strictly reads the materialized state in state.md and journal.md, refuses to fabricate missing details, and points to the appropriate sources for provenance.

When should I avoid using a read-only state reader for manager inquiries?

Avoid using a read-only state reader when you need to update project status or write new decisions. This approach is strictly for querying the materialized state, providing grounded answers from state.md and journal.md without modifying any workspace data.