Jarvis Test Gap Finder 01

Find missing tests by failure mode and business impact. Use when handling development work that needs repeatable steps, quality gates, and practical outputs.

Security Scan

This is a self-contained, instruction-only playbook for finding test gaps and producing action plans; its requirements and instructions align with its stated purpose.

Purpose & Capability

Name and description match the SKILL.md content: a test-gap playbook that produces checklists, checkpoints, and action plans. The skill requests no binaries, env vars, installs, or config paths — all proportional to a guidance-style skill.

Instruction Scope

SKILL.md contains high-level, reusable steps and output templates only; it does not instruct the agent to read system files, access external endpoints, or use credentials. The instructions are intentionally open-ended (asks the agent to define execution paths and checkpoints), so the agent may request additional context or artifacts from the user to produce concrete commands — this is expected for a playbook but grants the agent discretion to ask for more data.

Install Mechanism

No install spec and no code files are present. As an instruction-only skill, it writes nothing to disk and does not pull external code, which is low-risk.

Credentials

The skill requires no environment variables, credentials, or config paths. There are no requests for secrets or unrelated service keys, which is proportionate for the described purpose.

Persistence & Privilege

always:false and normal model invocation are set. The skill does not request persistent presence or elevated privileges and does not modify other skills or system settings.

Assessment

This skill is a benign, text-only playbook for producing test-gap analyses and action plans. Before sharing artifacts (logs, screenshots, code) avoid sending sensitive credentials or secrets. If the agent returns commands or checklists intended to be run in your environment, review them carefully before executing. Expect the agent to ask for clarifying context (desired outcome, constraints, artifacts) to produce concrete steps — provide only the minimum necessary information. Because this skill is generic and open-ended, verify ownership, ETAs, and fallback steps in any plan it produces before applying changes in production.

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."