openspec-plus-tasks Eval report.

Validation plan

What the agent should do next

1. 1Inspect repository, README/SKILL.md, license, and recent commits before production use.
2. 2Install in an isolated workspace or sandbox with no production secrets available.
3. 3Run the smallest representative task and record files touched, commands run, network access, and outputs.
4. 4Compare the selected skill against at least one alternative when the eval status is review or failed.
5. 5Promote only after the agent reports a successful verification result and unresolved warnings are accepted.

Do not use when

Conditions that require another skill

• teams that need a vendor-supported SLA
• production agents without a repository review
• SKILL.md is very strict about not reading source code and not writing implementation code, which is intentional, but it relies heavily on the design document being complete. If the design is incomplete, the skill correctly says to surface the gap, but this could still create friction in practice.
• High-risk permission hints: Shell or command execution, Secrets or environment access
• Dependency or permission surface needs review
• Permission surface may require sandboxing