Aggregate Mothership project status from local config and checkpoints.
npx skills add https://github.com/howdycarter/Mothership --skill status-howdycarter
Please help me install this Agent Skill. Skill: status Source: https://github.com/howdycarter/Mothership/tree/main/.claude/skills/status Command: npx skills add https://github.com/howdycarter/Mothership --skill status-howdycarter
Team members need a single source of truth for the Mothership project's health; this skill surfaces current state from local config and checkpoints to reduce context-switching and misalignment.
Ask the AI to fetch and display the current Mothership project status.
High-intent search queries and answers about installing and using this skill.
To check the Mothership project status, you can use a skill that reads local configuration and checkpoints to identify the project state. It aggregates data to provide a structured snapshot showing counts by status, recent activity, and the current git branch.
Tracking workflow statuses across stories and branches requires surfacing local checkpoint data. A status snapshot categorizes all stories into ready, in_progress, done, or blocked states, providing a quick verification of project health.
Project status aggregation works by reading local configuration files and checkpoints to determine the project state. It extracts story statuses and current git branch information, formatting them into a snapshot for quick verification and planning.
Yes, you can generate a real-time snapshot for project planning by reading local config and checkpoints. The resulting status snapshot includes story counts by status, recent activity, and current git branch context for stakeholders.
No, this project status tool does not require external dependencies to function. It operates by reading local configuration and checkpoint data directly to surface the current Mothership project state without additional packages.
You need to use a checkpoint-based status snapshot when team members require a single source of truth for project health. It reduces context-switching and misalignment during planning by surfacing current state from local configuration.
chriscarteruxRetrieve Mothership project status, configuration, git branch, and story breakdowns.
thesaifalitaiPlan agile software delivery with sprint backlogs, user stories, and release checklists.
dyoshikawaIdentify and delete stale local and remote-tracking git branches.
Cbanzaime23Parse epic files to generate a deterministic sprint-status.yaml for project tracking.
