Name: kingdom-status
Author: oliversl1vka

Prompt file imported from oliversl1vka/Kingdom (.github/prompts/kingdom-status.prompt.md). Copyright stays with the author.

Workflow

Generate a clean status report for the current KingdomOS state.

Step 1: Gather Core Health

Read kingdom.config.json.
Run node packages/cli/dist/index.js doctor --json first.
Use direct DB queries against kingdom/kingdom.db to fill any missing detail.

Step 2: Report The Current State

Include all of the following when available:

objective title and status
task breakdown by status
job breakdown by status
active file locks with owning job IDs
running or streaming jobs with tier, title, and timing
stuck tasks in awaiting-healer, awaiting-redesign, or stalled
total token usage and tier breakdown if available
recent failures with failure type and task title
diff success rate, with a flag when failure rate is high
file contention risk, especially the same files appearing in multiple active jobs

Step 3: Operational Interpretation

End with a one-line verdict:

HEALTHY
NEEDS ATTENTION
CRITICAL

State the primary reason.

Step 4: Patience Rule

If Squire jobs are merely slow but still progressing or heartbeating, do not classify the run as critical just because completion is taking time.

## Workflow Generate a clean status report for the current KingdomOS state. ### Step 1: Gather Core Health 1. Read `kingdom.config.json`. 2. Run `node packages/cli/dist/index.js doctor --json` first. 3. Use direct DB queries against `kingdom/kingdom.db` to fill any missing detail. ### Step 2: Report The Current State Include all of the following when available: 1. objective title and status 2. task breakdown by status 3. job breakdown by status 4. active file locks with owning job IDs 5. running or streaming jobs with tier, title, and timing 6. stuck tasks in `awaiting-healer`, `awaiting-redesign`, or `stalled` 7. total token usage and tier breakdown if available 8. recent failures with failure type and task title 9. diff success rate, with a flag when failure rate is high 10. file contention risk, especially the same files appearing in multiple active jobs ### Step 3: Operational Interpretation End with a one-line verdict: - `HEALTHY` - `NEEDS ATTENTION` - `CRITICAL` State the primary reason. ### Step 4: Patience Rule If Squire jobs are merely slow but still progressing or heartbeating, do not classify the run as critical just because completion is taking time.

{ "prompt": "## Workflow\r\n\r\nGenerate a clean status report for the current KingdomOS state.\r\n\r\n### Step 1: Gather Core Health\r\n\r\n1. Read `kingdom.config.json`.\r\n2. Run `node packages/cli/dist/index.js doctor --json` first.\r\n3. Use direct DB queries against `kingdom/kingdom.db` to fill any missing detail.\r\n\r\n### Step 2: Report The Current State\r\n\r\nInclude all of the following when available:\r\n\r\n1. objective title and status\r\n2. task breakdown by status\r\n3. job breakdown by status\r\n4. active file locks with owning job IDs\r\n5. running or streaming jobs with tier, title, and timing\r\n6. stuck tasks in `awaiting-healer`, `awaiting-redesign`, or `stalled`\r\n7. total token usage and tier breakdown if available\r\n8. recent failures with failure type and task title\r\n9. diff success rate, with a flag when failure rate is high\r\n10. file contention risk, especially the same files appearing in multiple active jobs\r\n\r\n### Step 3: Operational Interpretation\r\n\r\nEnd with a one-line verdict:\r\n\r\n- `HEALTHY`\r\n- `NEEDS ATTENTION`\r\n- `CRITICAL`\r\n\r\nState the primary reason.\r\n\r\n### Step 4: Patience Rule\r\n\r\nIf Squire jobs are merely slow but still progressing or heartbeating, do not classify the run as critical just because completion is taking time.", "variables": [], "notes": "Produce a high-signal real-time status snapshot for the current KingdomOS run, including health, blockers, contention, and a final verdict.", "metadata": { "source": { "provider": "github-prompts", "repository": "https://github.com/oliversl1vka/Kingdom", "path": ".github/prompts/kingdom-status.prompt.md", "ref": "436a7cb2b25b19a7b195845fcd74d329b29b43ee", "url": "https://github.com/oliversl1vka/Kingdom/blob/436a7cb2b25b19a7b195845fcd74d329b29b43ee/.github/prompts/kingdom-status.prompt.md", "key": "oliversl1vka/Kingdom/.github/prompts/kingdom-status.prompt.md" } } }

kingdom-status

About

Workflow

Step 1: Gather Core Health

Step 2: Report The Current State

Step 3: Operational Interpretation

Step 4: Patience Rule

Use it

Manifest

Reviews