x
Jarvis Incident Timeline Writer 01
Verified@xammarie
npx machina-cli add skill @xammarie/jarvis-incident-timeline-writer-01 --openclawFiles (1)
SKILL.md
1.3 KB
Jarvis Incident Timeline Writer 01
Deliver a concrete, reusable workflow for development tasks.
Inputs
- Desired outcome and deadline
- Constraints (time, tools, risk tolerance)
- Available artifacts (code, docs, screenshots, logs)
Playbook
- Define success and failure criteria in measurable terms.
- Build a smallest-valid execution path before scaling effort.
- Execute in checkpoints; record evidence at each checkpoint.
- Apply quality gates before finalizing recommendations.
- Return implementation-ready outputs and next actions.
Quality Gates
- Evidence-backed claims only.
- Explicit assumptions and tradeoffs.
- Reversible changes preferred for risky operations.
- Clear owner + ETA for each next step.
- Include a fallback if the primary plan fails.
Output Format
- Situation summary (5 lines max)
- Top findings (ranked by impact)
- Action plan (today / this week)
- Risks + mitigations
- Exact checklist or commands where useful
Example prompts
- "Use this skill to turn my messy notes into a production-ready plan."
- "Run this skill and give me a risk-first action sequence with acceptance checks."
Overview
Jarvis Incident Timeline Writer delivers a concrete, reusable workflow for development tasks by turning logs, notes, and artifacts into a repeatable incident timeline. It defines measurable success criteria, checkpoints, and quality gates to produce implementation-ready outputs and clear next steps.
How This Skill Works
Inputs include desired outcome, deadline, constraints, and available artifacts. The playbook then guides you to define success criteria, build a smallest-valid execution path, run checkpoints with evidence at each step, apply quality gates, and return implementation-ready outputs with next actions.
When to Use It
- When you need repeatable development steps and quality gates for incidents.
- When converting messy notes and logs into a production-ready incident plan.
- When you must define measurable criteria and checkpoints before acting.
- When you want implementation-ready outputs and clear next actions.
- When you require an evidence-backed action sequence with acceptance checks.
Quick Start
- Step 1: Gather inputs (desired outcome, deadline, constraints, artifacts like code/docs/logs).
- Step 2: Run the playbook: define measurable criteria, build smallest path, set checkpoints, apply quality gates.
- Step 3: Generate outputs: situation summary, top findings, action plan, risks + mitigations, exact checklist.
Best Practices
- Define success and failure criteria in measurable terms.
- Build the smallest-valid execution path before scaling effort.
- Execute in checkpoints; record evidence at each checkpoint.
- Apply quality gates with reversible changes and explicit owners.
- Include a fallback plan and ETA for each next step.
Example Use Cases
- Turning a collection of incident notes into a production-ready incident timeline with checkpoints.
- Generating a risk-prioritized action sequence that includes acceptance checks.
- Delivering an implementation-ready task plan with a clear owner and ETA.
- Producing a quality-gated deployment checklist from logs and docs.
- Creating an exact checklist or commands to reproduce and resolve an incident.
Frequently Asked Questions
Add this skill to your agents