Jarvis Bug Triage 01

Triage production bugs fast with repro isolation and risk-first fixes. Use when handling development work that needs repeatable steps, quality gates, and pra...

Security Scan

This is a high-level, instruction-only triage playbook whose requirements and instructions are coherent with its stated purpose and do not request extra access or installs.

Purpose & Capability

The name/description (bug triage, repro isolation, risk-first fixes) matches the SKILL.md playbook. There are no requested binaries, environment variables, or install steps that don't belong to a triage workflow.

Instruction Scope

The instructions are high-level and constrained to producing a reproducible workflow, checkpoints, evidence, risks, and action items. The playbook does not instruct the agent to read system files, access credentials, or transmit data externally, but it is intentionally open-ended (asks for 'available artifacts' and to 'record evidence'), so the agent may request user-provided logs or snippets — users should avoid sharing secrets.

Install Mechanism

No install spec and no code files — instruction-only skill. This minimizes disk write and supply-chain risk.

Credentials

No environment variables, credentials, or config paths are required. The skill does not request unrelated secrets or system access.

Persistence & Privilege

Defaults are used (not always: true). The skill does not request permanent presence or elevated privileges and does not modify other skills or system-wide settings.

Assessment

This skill is an instruction-only triage playbook and is internally coherent. It poses low technical installation risk, but be cautious about the data you provide when using it: do not paste credentials, API keys, unredacted PI, or full production secrets into prompts or logs. If the skill outputs shell commands or remediation steps, review and test them in a safe environment before running them in production. If you prefer tighter control, only invoke the skill interactively (don’t enable any automated/autonomous execution) and scrub logs or artifacts before sharing.

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

1. Define success and failure criteria in measurable terms.
2. Build a smallest-valid execution path before scaling effort.
3. Execute in checkpoints; record evidence at each checkpoint.
4. Apply quality gates before finalizing recommendations.
5. 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."