Resolve Findings
Developmentresolve-findingsResolve Findings is an Agent Skill for development published in the Agenta-AI/agenta repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Resolve findings by implementing the chosen fix path in code, tests, or docs. Accept optional `path` and a `priority` selector; by default resolve only the next highest remaining priority bucket, in order `P0`, `P1`, `P2`, `P3`. Also accept explicit levels or `all`. Default to `path=infer`. Confirm effective variables before starting.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/Agenta-AI/agenta/blob/HEAD/agents/skills/resolve-findings/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/resolve-findings, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Resolve Findings
Read these shared references when needed:
../shared/references/findings.schema.md../shared/references/findings.lifecycle.md
Role
Resolve is execution mode from findings back into code, tests, and docs.
- It may change production code for verification findings.
- It may change tests or test harnesses for validation findings.
- It should update the active findings record after implementation and rerun targeted checks when feasible.
Priority Input
Accept a priority parameter from the prompt:
- omitted priority: resolve the next highest remaining bucket only
- explicit level:
P0,P1,P2, orP3 all: resolve all remaining buckets
Default:
priority=next-highest
Path Input
Accept an optional path from the prompt.
- If
pathis provided, use it as the local design or findings folder. - If
pathis omitted, infer it from the branch, subsystem, or matching docs and state the inferred value before starting.
Default:
path=infer
Workflow
-
Determine the selected bucket. Confirm the effective variables first:
pathpriority- target findings files when inferable
Use the requested
priority, or the next highest unresolved bucket in the active findings record. -
Load the active findings record. Use
path/findings.md. -
Check readiness before coding. If the intended resolution path, policy boundary, or data contract is still ambiguous, ask the next follow-up question before editing.
-
Implement the selected fixes. Make the smallest coherent set of code, test, and doc changes needed for the selected findings bucket.
-
Re-run targeted checks. Use the narrowest useful verification or validation pass that demonstrates the fix.
-
Update the findings record. Move findings between open and closed sections, preserve notes and open questions ordering, and record what was fixed or what remains blocked.
Rules
- Do not hide ambiguity behind
openorneeds-user-decisionwhen the user already started answering. Ask the next concrete question. - Do not silently widen scope from the selected priority bucket unless the fix is tightly coupled.