triage

Files (28)

• README.md
• SKILL.md
• analyze.md · commands/
• assess.md · commands/
• report.md · commands/
• run.md · commands/
• scan.md · commands/
• start.md · commands/
• guidelines.md
• ai-synthesis.schema.json · schemas/
• analyzed.schema.json · schemas/
• finalize_analysis.py · scripts/
• prepare_analysis.py · scripts/
• prepare_report.py · scripts/
• render_report.py · scripts/
• scan.py · scripts/
• synthesize_report.py · scripts/
• test_prepare_analysis.py · scripts/
• test_render_report.py · scripts/
• test_scan.py · scripts/
• test_token_optimization.py · scripts/
• analyze.md · skills/
• assess.md · skills/
• report.md · skills/
• run.md · skills/
• scan.md · skills/
• start.md · skills/
• report.html · templates/

SKILL.md (first lines)

# Triage Workflow Orchestrator

## Quick Start

1. If the user invoked `/run`, read `skills/run.md` and follow it — this drives all phases end-to-end without pausing
2. If the user invoked `/assess`, read `skills/assess.md` and follow it — full single-issue triage in chat (does not write `analyzed.json` / `report.html`)
3. If the user invoked a specific bulk phase command (`/start`, `/scan`, `/analyze`, `/report`), read the corresponding skill file from `skills/{phase}.md` and execute it
4. If the user provided a Jira project key but no specific command, start with `skills/start.md` to validate access and create the workspace, then proceed to `skills/scan.md`
5. If no project key was provided, start with `skills/start.md` to gather it

If a step fails or produces unexpected output, stop and report the error to the
user. Do not advance to the next phase. Offer to retry the failed step or
escalate.

For principles, hard limits, safety, quality, and escalation rules, see `guidelines.md`.

From flightctl/ai-workflows, MIT.

More from flightctl/ai-workflows