rtexit-method 0.1.0 → 0.1.1

package/packaged-assets/.agents/skills/rt-status/SKILL.md

@@ -0,0 +1,64 @@
+---
+name: rt-status
+description: "Show current engagement status dashboard — active phase, finding counts by severity, timeline summary, recommended next action. Use anytime to get a quick overview of engagement progress."
+---
+
+# rt-status
+
+# Engagement Status Dashboard
+
+## Display the following:
+
+### Current Engagement
+Load from: `_rtexit-output/docs/engagement/engagement-info.json`
+Show: ref, client, start date, days remaining, methodology
+
+### Findings Summary
+Run: `python3 {project-root}/_rtexit/scripts/finding_tracker.py stats`
+Display statistics by severity.
+
+### Recent Activity
+Load from: `_rtexit-output/docs/engagement/timeline.md`
+Show last 10 timeline entries.
+
+### Phase Progress
+Estimate current phase completion:
+- Phase 1 (Planning): SEAD + scope + threat model created?
+- Phase 2 (Recon): Attack surface map created?
+- Phase 3 (Exploitation): High-priority targets tested?
+- Phase 4 (Reporting): Executive report drafted?
+
+### Recommended Next Action
+Based on phase and findings, suggest what to do next.
+If Phase 2 complete but Phase 3 not started: "Start with highest-priority exploitation targets from attack surface map"
+If critical findings not documented: "Document and CVSS-score all critical findings"
+
+## Operator Checklist
+
+| Area | Question |
+|---|---|
+| Authorization | Does SEAD exist and is it current? |
+| Scope | Are targets and exclusions documented? |
+| Phase | Planning, Recon, Exploitation, Reporting, or Retest? |
+| Findings | How many open findings by severity? |
+| Evidence | Are evidence files linked and hashed? |
+| Next Action | Which RTExit skill should run next? |
+
+## Output Format
+
+```markdown
+# RTExit Status
+Engagement: [REF]
+Client: [CLIENT]
+Current Phase: [PHASE]
+Authorization: [OK/MISSING/EXPIRED]
+Critical: 0 | High: 0 | Medium: 0 | Low: 0
+Recommended Next Step: [skill + reason]
+```
+
+## Failure Modes
+
+- If config is missing, recommend `resolve_config.py` and show the missing path.
+- If SEAD is missing, route to `rt-create-sead`.
+- If findings exist without evidence, route to `rt-evidence-chain`.
+- If exploitation is requested before scope exists, route to `rt-scope-definition`.