skill-system-review
Bridge between OMO Prometheus and TKT ticket lifecycle. Generates structured review context for Prometheus after bundle close, converts Prometheus plans into TKT bundle commands, writes review feedback into the Review Agent Inbox, and provides a structured question protocol for gathering information efficiently. Load this skill when you need to: (1) generate a review prompt for a completed ticket/bundle, (2) convert a Prometheus plan.md into TKT worker tickets, (3) write review feedback back into the ticket system, (4) ask structured questions using the question tool across all scenarios (requirements, decisions, review, planning).
What this skill does
# skill-system-review
Bridge between OMO Prometheus and the TKT ticket lifecycle.
**Two directions**:
1. **Review** — After bundle closes, assemble structured review context for Prometheus to evaluate
2. **Plan→TKT** — Convert Prometheus plans into TKT roadmap bundles and worker tickets
## Operations
### generate-review-prompt
Generate a structured review context from a completed/active ticket for Prometheus review.
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" generate-review-prompt --ticket-id <TKT-XXX>
```
**Input**: `--ticket-id` (required) — the ticket to build review context for
**Output**: JSON with `review_context`, `prometheus_prompt`, `expected_output_format`
Reads:
- Bundle `review.yaml` (stub generated by `tkt.sh close`)
- All completed ticket results in the bundle
- Audit ticket (TKT-A00) findings
- Current `roadmap.yaml` state
### generate-startup-review-prompt
Generate a review overview prompt for Prometheus at session startup (no active ticket context).
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" generate-startup-review-prompt
```
**Output**: JSON with `roadmap_summary`, `bundles`, `prometheus_prompt`
### generate-startup-review
Generate a compact startup context summary for the next session.
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" generate-startup-review
```
**Output**: JSON with `context_summary`, `roadmap_summary`, `bundles`
- includes `carryover_bundles[]` when reviewed bundles still have carryover work
### suggest-roadmap-update
Suggest roadmap changes from findings/issues without mutating `roadmap.yaml`.
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" suggest-roadmap-update --input findings.json
```
**Output**: JSON `suggestions[]` with `{phase, section, change_type, description, rationale}`
### plan-to-bundle
Convert a Prometheus plan file (`.sisyphus/drafts/*.md`) into TKT bundle creation commands.
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" plan-to-bundle --plan-file <path>
```
**Input**: `--plan-file` (required) — path to Prometheus plan markdown
**Output**: JSON with `route`, `goal`, `tickets[]`, `tkt_commands[]` (ready-to-execute shell commands)
Parsing rules:
- `## ` or `### ` headings with TODO/task keywords → ticket titles
- `- [ ]` checkboxes → individual worker tickets
- Dependency markers (`depends on`, `after`, `blocks`) → `depends_on` fields
- Effort estimates → ticket description metadata
- Categories (`visual-engineering`, `deep`, `quick`, etc.) → ticket `category`
- `### WAVE N` headings → ticket `wave` metadata for following tasks
- Structured ticket metadata lines (category, effort, acceptance, source metadata, skills, QA scenarios) → preserved into ticket objects and generated TKT commands
- Tiny plans can route to express without filename mentions when they stay within the no-dependency, no-effort fast path
### write-review-inbox
Write Prometheus review feedback into the Review Agent Inbox format for `refresh_review_inbox()` ingestion.
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" write-review-inbox --input <json-file>
```
**Input**: JSON file with `discussion_points[]`, `next_actions[]`, `batch_id`
**Output**: Appends `## Review Agent Inbox` + `# TICKET_BATCH` section to `note/note_tasks.md`
### generate-dispatch
Generate a worker dispatch view from bundle ticket state.
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" generate-dispatch --bundle B-001 [--tickets TKT-001,TKT-002]
python3 "<this-skill-dir>/scripts/review_prompt.py" generate-dispatch --auto
```
**Input**: `--bundle` (required), optional `--tickets` comma list
**Output**: human-readable wave summary plus last-line JSON containing grouped dispatch waves
Rules:
- without `--tickets`, emit currently open worker tickets only
- preserve bundle dependency order into `dispatch_wave`
- include one-line summary and effort estimate for each ticket
- `--auto` creates the suggested next bundle from `suggest-next-bundle` and immediately emits dispatch for it
### suggest-next-bundle
Suggest the next bundle goal and seed tickets from roadmap/open work/carryover.
```bash
python3 "<this-skill-dir>/scripts/review_prompt.py" suggest-next-bundle
```
**Output**: JSON with `goal`, `suggested_tickets[]`, `open_issues[]`
## Integration with OMO Prometheus
### Prometheus as Review Agent
When a TKT bundle closes:
1. `tkt.sh close` generates `review.yaml` stub
2. PM Agent calls `generate-review-prompt` to assemble review context
3. Prometheus receives the structured context and produces:
- `summary` — what was accomplished
- `discussion_points[]` — trade-offs, concerns, questions for user
- `next_actions[]` — follow-up work items
- `quality_assessment` — structured quality evaluation
4. `write-review-inbox` converts Prometheus output into TKT-ingestible tickets
5. `refresh_review_inbox()` picks up new tickets automatically
### Prometheus as Roadmap Planner
When a user makes a new request through Prometheus:
1. Prometheus conducts structured interview (OMO default behavior)
2. Prometheus writes plan to `.sisyphus/drafts/`
3. `plan-to-bundle` reads the plan and generates TKT commands
4. PM Agent executes the commands to create roadmap goal + bundle + worker tickets
5. OMO dispatches agents to claim and execute tickets
### Prompt Reference
- `prompts/prometheus-tkt-integration.md` — Instructions for Prometheus on how to use TKT roadmap/bundle system
- `prompts/question-protocol.md` — Structured questioning guide for all scenarios (requirements, branch decisions, review discussion, roadmap planning). Implements the `question_tool_first` policy from `config/tkt.yaml`.
## Compatibility
- **tickets.py alignment**: `review_prompt.py` path matches the hardcoded reference at `tickets.py:2468-2470`
- **Review Inbox format**: Output matches `parse_review_agent_inbox()` expected format (`## Review Agent Inbox` + `# TICKET_BATCH`)
- **Scope rules**: Referenced in 14+ ticket scope `allowed_prefixes` entries in `tickets.py`
```skill-manifest
{
"schema_version": "2.0",
"id": "skill-system-review",
"version": "1.0.0",
"capabilities": [
"review-generate",
"review-startup",
"review-startup-summary",
"review-roadmap-suggestion",
"review-plan-to-bundle",
"review-generate-dispatch",
"review-suggest-next-bundle",
"review-write-inbox"
],
"effects": ["fs.read", "fs.write"],
"operations": {
"generate-review-prompt": {
"description": "Assemble structured review context from completed ticket/bundle for Prometheus",
"input": { "ticket_id": { "type": "string", "required": true } },
"output": { "description": "Review context JSON", "fields": { "review_context": "object", "prometheus_prompt": "string" } },
"entrypoints": {
"unix": ["python3", "{skill_dir}/scripts/review_prompt.py", "generate-review-prompt", "--ticket-id", "{ticket_id}"]
}
},
"generate-startup-review-prompt": {
"description": "Generate Prometheus review overview at session startup",
"input": {},
"output": { "description": "Startup review context JSON", "fields": { "roadmap_summary": "object", "bundles": "array", "prometheus_prompt": "string" } },
"entrypoints": {
"unix": ["python3", "{skill_dir}/scripts/review_prompt.py", "generate-startup-review-prompt"]
}
},
"generate-startup-review": {
"description": "Generate compact startup context summary from roadmap and recent bundle reviews",
"input": {},
"output": { "description": "Startup summary JSON", "fields": { "context_summary": "string", "roadmap_summary": "object", "bundles": "array" } },
"entrypoints": {
"unix": ["python3", "{skill_dir}/scripts/review_prompt.py", "generate-startup-review"]
}
},
"suggest-roadmap-update": {
"description": "Suggest roadmap updates from findings/issues without mutating roadmap.yaml",
"input": {
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.