j.status

Prints a human-readable summary of the scrum board, open rapports, and pending queue triggers.

Updated Aug 3, 2026
One-click install
npx skills add https://github.com/samwelmunga/jenga-npm --skill j-status-samwelmunga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: j.status
Source: https://github.com/samwelmunga/jenga-npm/tree/main/.agents/skills/j-status
Command: npx skills add https://github.com/samwelmunga/jenga-npm --skill j-status-samwelmunga

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? When working across multiple AI-assisted development sessions, it is hard to know the current state of the project without manually reading every board file. This Skill aggregates epics, stories, tasks, open rapports, and pending queue triggers into one readable overview. ## Core Features & Use Cases - Board Summary: Scans project/board/ epics, stories, and tasks and prints their statuses in a hierarchical, icon-annotated tree. - Rapport & Queue Visibility: Lists open problem and analysis rapports plus the count of unprocessed scrum master triggers in the queue. - Collision-Safe Alias: Provides the same behavior as /status under the j-status directory name so it is not shadowed by a host tool's built-in command. - Use Case: At the start of a session, ask for the project status to instantly see which tasks passed, which are in progress, and whether any triggers await the scrum master. ## Quick Start Ask the agent to show the current project status and board overview using j-status.

Frequently Asked Questions about j.status

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

FAQPage Schema
How do I get a quick overview of my scrum board status?▼

Invoke the status skill to scan all epic, story, and task files under project/board/ and print a hierarchical summary with status icons. It also lists open rapports and pending queue triggers in the same output.

What is the difference between /status and /j-status?▼

Both run identical logic; j-status is a directory-name alias that guarantees the skill is reachable even when a host tool's built-in command shadows the bare /status name. It is generated from the source status skill by a sync script.

Does the status summary include playbook run state?▼

No. The skill reports board-level status only from project/board/ files. Playbook run state is ephemeral, session-local execution data and is intentionally never read or reported by this skill.

Why does the status output say no board items found?▼

That message appears when no epic files exist in project/board/epics/. Run the planning skill (/pi-plan) to define epics or /todo to add items, then re-run the status check.

Can I edit the j-status SKILL.md file directly?▼

No. The file is generated and synced by scripts/generate-j-alias.sh from the source skills/status/SKILL.md. Hand edits are overwritten; re-run the generator to pick up source changes.