50fa79407d
Public, sanitized mirror of an AI orchestration command center: agents, skills, MCP servers, slash-command workflows. All infrastructure identifiers, hostnames, mesh IPs/subnets, repo paths, maintainer identity, and hardware fleet specifics scrubbed to <placeholders>; session debug logs and host-specific memory removed. No live credentials. Verified clean by automated leak sweep. See SANITIZATION.md. churchofmalware.org . authorized research only
3.2 KiB
Track — Know Where Things Stand
Tracking operations use bash scripts directly for speed and consistency. The LLM is not needed for these — just run the script and present the output.
Script-First Rule
All tracking operations have a corresponding bash script. Run the script; do not reconstruct the output manually.
Scripts live in references/scripts/ relative to this skill, but need to run from the project root (where .claude/ lives). Run them as:
bash <skill_path>/references/scripts/<script>.sh [args]
Or if ccpm is installed project-locally:
bash ccpm/scripts/pm/<script>.sh [args]
Project Status
Trigger: "what's our status", "project status", "overview"
bash references/scripts/status.sh
Shows: active epics, open issues count, recent activity.
Standup Report
Trigger: "standup", "daily standup", "what did we do", "morning update"
bash references/scripts/standup.sh
Shows: what was completed yesterday, what's in progress today, any blockers.
List Epics
Trigger: "list epics", "show epics", "what epics do we have"
bash references/scripts/epic-list.sh
Show Epic Details
Trigger: "show the epic", "epic details for "
bash references/scripts/epic-show.sh <name>
Epic Status
Trigger: "status of the epic", "how far along is "
bash references/scripts/epic-status.sh <name>
Shows: task completion breakdown, active agents, blocking issues.
List PRDs
Trigger: "list PRDs", "what PRDs do we have", "show backlog"
bash references/scripts/prd-list.sh
PRD Status
Trigger: "PRD status", "which PRDs are parsed", "what's in backlog"
bash references/scripts/prd-status.sh
Search
Trigger: "search for ", "find issues about ", "look for "
bash references/scripts/search.sh "<query>"
Searches local task files, PRDs, and epics for the query term.
What's In Progress
Trigger: "what's in progress", "what are we working on", "active work"
bash references/scripts/in-progress.sh
What's Next
Trigger: "what should I work on next", "what's next", "next priority"
bash references/scripts/next.sh
Shows highest-priority open tasks with no blocking dependencies.
What's Blocked
Trigger: "what's blocked", "any blockers", "what can't we move on"
bash references/scripts/blocked.sh
Validate Project State
Trigger: "validate", "check project state", "is everything consistent"
bash references/scripts/validate.sh
Checks: frontmatter consistency, orphaned files, missing GitHub links, dependency integrity.
When Scripts Fail
If a script fails or the output needs interpretation (e.g., an error in the output, or the user asks "what does this mean"), then step in to explain. But always run the script first — don't guess at what status/standup output would look like.
If .claude/ directory doesn't exist at all, the project hasn't been initialized. Direct the user to run:
bash references/scripts/init.sh