For
Use it when the work needs a boundary.
Developers and maintainers who want a disciplined path from uncertain report to evidence-backed repair.
Report → minimal repair
Stop guessing at vague bug reports.
Move from symptoms to a reproducible case, evidence-supported root cause, minimally scoped fix, and regression protection.
Single-user license · 7-day refund window · 12 months of maintenance updates
01 / Outcome
A reviewable artifact, not a confident paragraph.
A repair plan that distinguishes what reproduced, what did not, why the smallest fix is sufficient, and how the original failure will stay fixed.
When the evidence is incomplete, the workflow narrows the conclusion, marks the gap, and returns the next verification instead of inventing project facts.
02 / Workflow
6 focused skills, each with one job.
- 01
Triage
An actionable issue without premature diagnosis
- 02
Reproduce
A repeatable case or bounded non-reproduction report
- 03
Isolate
The smallest supported cause and ruled-out alternatives
- 04
Plan the fix
A narrow correction with controlled regression surface
- 05
Write regression tests
Proof of the repaired invariant
- 06
Review the incident
A learning record focused on the system
03 / Fictional demonstration
Worked example: timezone double-booking
A fictional DST defect appears only on the reschedule path. The workflow isolates a naive-local-versus-UTC comparison and keeps the repair at the scheduling authority boundary instead of weakening collision rules globally.
This excerpt is a fictional demonstration. It is not a customer result, production test, approval, or performance claim.
Confirmed scope
Reschedule path, Europe/Bucharest, spring DST boundary
Minimal repair
Normalize the candidate through the existing timezone-aware boundary
Regression proof
DST gap, equivalent UTC intervals, adjacent slots, control dates
04 / Included
Everything needed to install, adapt, and inspect the workflow.
- 6 native SKILL.md workflows
- 6 portable prompts
- 6 reusable Markdown templates
- 3 realistic worked examples
- Quick-start PDF, compatibility guide, license, and 12 months of maintenance updates
Not for
Keep the limits visible.
Buyers expecting the pack to inspect a private repository, logs, or production system without providing access and evidence.
05 / Questions
Compatibility, evidence, and execution.
Is this a generic prompt collection?
No. Each workflow has a narrow trigger, required inputs, a procedure, an output contract, and rules for handling missing evidence.
Which assistants are supported?
The native filesystem skills are designed for Codex and Claude custom Agent Skills. Portable copy-and-paste prompts are included for other assistants. Availability depends on the model, plan, tools, and permissions you use.
Does the pack run code or change systems automatically?
No bundled workflow contains scripts or hidden network calls. A workflow may guide an assistant that already has tools, but consequential actions still require the user's authorization.
Are outcomes guaranteed?
No. Results depend on the context supplied, available evidence, model capability, tool access, and human review.
Replace improvised prompting with a reviewable workflow.
Native skills, portable prompts, templates, worked examples, and a practical quick start.