Slash Command

/status

Synthesize the current state of the project from `.context/`. Useful for onboarding, catching up after a break, or getting the big picture.

npx claudepluginhub littlelingo/context-engine --plugin context-engine

Prompt Preview

# /status - Project Briefing

Synthesize the current state of the project from `.context/`. Useful for onboarding, catching up after a break, or getting the big picture.

This command is read-only. It doesn't modify anything.

## Process

1. **Read project knowledge** (in this order, skip any that don't exist):
   - `.context/architecture/OVERVIEW.md` - what the project is
   - `.context/architecture/TECH_STACK.md` - languages, frameworks, commands
   - `.context/features/FEATURES.md` - what's been built and what's in progress
   - `.context/knowledge/LEARNINGS.md` - recent insights (last 5...

Command Content

Other plugins with /status

/status

32.9k

Display Conductor project status including overall progress, active tracks summary, and next actions. Optional [track-id] [--detailed] for per-track task details and blockers.

conductor

/status

20.1k

Displays compact planning status from task_plan.md: current phase and progress, phase list with icons, error count, and planning file checks.

planning-with-files

/status

11.4k

Shows 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.

1 tool

codex

/status

4.7k

Displays 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.

interface-design

/status

2.8k

Checks current session status and measures goal drift to assess alignment and progress in the conversation.

ouroboros

/status

2.7k

Displays 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.

1 tool

all-commands

Stats

Stars1

Forks0

Last CommitMar 22, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

# /status - Project Briefing Synthesize the current state of the project from `.context/`. Useful for onboarding, catching up after a break, or getting the big picture. This command is read-only. It doesn't modify anything. ## Process 1. **Read project knowledge** (in this order, skip any that don't exist): - `.context/architecture/OVERVIEW.md` - what the project is - `.context/architecture/TECH_STACK.md` - languages, frameworks, commands - `.context/features/FEATURES.md` - what's been built and what's in progress - `.context/knowledge/LEARNINGS.md` - recent insights (last 5...

/status - Project Briefing

Synthesize the current state of the project from .context/. Useful for onboarding, catching up after a break, or getting the big picture.

This command is read-only. It doesn't modify anything.

Process

Read project knowledge (in this order, skip any that don't exist):

.context/architecture/OVERVIEW.md - what the project is
.context/architecture/TECH_STACK.md - languages, frameworks, commands
.context/features/FEATURES.md - what's been built and what's in progress
.context/knowledge/LEARNINGS.md - recent insights (last 5-10 entries)
.context/errors/INDEX.md - number of known error patterns
.context/patterns/CODE_PATTERNS.md - number of documented patterns

Present a briefing covering: project summary, tech stack, features (completed/in-progress/planned with current step), last 3-5 learnings, knowledge base counts (patterns, errors, ADRs), and next action (resume command or research suggestion).

If $ARGUMENTS contains "onboard" or "new": Also include key dev commands, top 3 code patterns, top 3 error patterns, and architecture component map.

Rules

Read-only. Don't modify any files.

Keep it concise. This is a briefing, not a book.

Prioritize actionable info: what's in progress, what was recently learned, what to do next.

If .context/ is mostly empty, say so and recommend running /init.

User Input

$ARGUMENTS

/status - Project Briefing

Synthesize the current state of the project from .context/. Useful for onboarding, catching up after a break, or getting the big picture.

This command is read-only. It doesn't modify anything.

Process

Read project knowledge (in this order, skip any that don't exist):
- .context/architecture/OVERVIEW.md - what the project is
- .context/architecture/TECH_STACK.md - languages, frameworks, commands
- .context/features/FEATURES.md - what's been built and what's in progress
- .context/knowledge/LEARNINGS.md - recent insights (last 5-10 entries)
- .context/errors/INDEX.md - number of known error patterns
- .context/patterns/CODE_PATTERNS.md - number of documented patterns
Present a briefing covering: project summary, tech stack, features (completed/in-progress/planned with current step), last 3-5 learnings, knowledge base counts (patterns, errors, ADRs), and next action (resume command or research suggestion).
If $ARGUMENTS contains "onboard" or "new": Also include key dev commands, top 3 code patterns, top 3 error patterns, and architecture component map.

Rules

Read-only. Don't modify any files.
Keep it concise. This is a briefing, not a book.
Prioritize actionable info: what's in progress, what was recently learned, what to do next.
If .context/ is mostly empty, say so and recommend running /init.

User Input

$ARGUMENTS