pactkit-status
npx machina-cli add skill pactkit/claude-code-plugin/pactkit-status --openclawPactKit Status
Read-only project state report. Provides sprint board summary, git state, and health indicators.
When Invoked
- Init Phase 6 (Session Context): Bootstrap initial context.
- Cold-start detection: Auto-invoked when session needs orientation.
Protocol
1. Gather Data
- Check if
docs/product/sprint_board.mdexists. - If yes: extract story counts by section (Backlog / In Progress / Done).
- Count Specs in
docs/specs/*.mdvs total board stories. - Check architecture graph freshness.
2. Git State
- Current branch, uncommitted changes, active feature branches.
3. Output Report
## Project Status Report
### Sprint Board
- Backlog: {N} stories
- In Progress: {N} stories
- Done: {N} stories
### Git State
- Branch: {current}
- Uncommitted: {Y/N}
### Health Indicators
- Architecture graphs: {fresh/stale/missing}
- Specs coverage: {N/N}
### Recommended Next Action
{Decision tree}
CONSTRAINT: This skill is read-only. It does not modify any files.
Source
git clone https://github.com/pactkit/claude-code-plugin/blob/main/pactkit-plugin/skills/pactkit-status/SKILL.mdView on GitHub Overview
PactKit Status provides a read-only report of the current project state, including sprint board counts, Git state, and health indicators. It supports cold-start orientation by surfacing what exists and what needs attention without modifying files.
How This Skill Works
On invocation, PactKit Status gathers data from the repository: it checks docs/product/sprint_board.md for Backlog/In Progress/Done counts, compares docs/specs/*.md coverage to board stories, and assesses architecture graph freshness. It also collects Git state information (current branch, uncommitted changes, active feature branches) and outputs a structured Project Status Report.
When to Use It
- Cold-start orientation for a new project to bootstrap initial context
- Init Phase 6 bootstrap to establish an orientation context without modifying files
- Onboarding new team members needing a quick project state summary
- Pre-sprint planning to confirm board status, spec coverage, and health indicators
- Quick health audit before a release or milestone
Quick Start
- Step 1: Invoke pactkit-status during Init Phase 6 or cold-start to gather data
- Step 2: Review the Project Status Report sections: Sprint Board, Git State, Health Indicators
- Step 3: Follow the Recommended Next Action to guide subsequent steps
Best Practices
- Ensure docs/product/sprint_board.md exists to enable accurate sprint counts
- Verify architecture graph freshness to reflect current system health
- Compare docs/specs/*.md coverage with sprint board stories to identify gaps
- Remember the report is read-only; do not modify repository files
- Use the Recommended Next Action in the output to drive immediate follow-ups
Example Use Cases
- Onboard a new PactKit plugin project by generating a status report at first session
- Audit an existing pactkit-status run before a major release to assess readiness
- Validate that sprint board counts align with the content of docs/product/sprint_board.md
- Check that specs in docs/specs/*.md adequately cover board stories
- Assess architecture graph freshness to flag missing or stale graphs
