execute-work

Implement agreed work outcomes with tests, verification, and recorded evidence.

1|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/pnewsam/skills --skill execute-work-pnewsam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-work
Source: https://github.com/pnewsam/skills/tree/main/registry/execute-work
Command: npx skills add https://github.com/pnewsam/skills --skill execute-work-pnewsam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Turning an agreed plan or issue into a verified code change often drifts: scope creeps, unrelated changes get tangled in, tests and documentation are skipped, and completion is claimed without evidence. This Skill implements one bounded work unit end to end while preserving unrelated work and recording proof. ## Core Features & Use Cases - Scoped Implementation: Makes the smallest coherent change satisfying all acceptance criteria, including tests, documentation, configuration, and migrations in the same unit. - Domain References: Loads focused guidance for security remediation, browser test repair, and architecture documentation only when the work requires it. - Review-Fix Loop: Verifies each review finding against the current candidate, fixes supported in-scope defects, and explains out-of-scope or unsubstantiated findings. - Use Case: Given a Linear issue describing a bug fix with acceptance criteria, implement the change, add regression tests, rerun the named measurement method, and record before/after evidence without committing until delivery is requested. ## Quick Start Use execute-work to implement the change described in this issue, including tests and verification evidence.

Frequently Asked Questions about execute-work

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I implement a planned feature with tests and evidence?▼

Read the work record and repository state, make the smallest coherent change satisfying all acceptance criteria, and add tests and documentation in the same unit. Rerun any named measurement method and record comparable before/after evidence.

How should I handle review feedback on my code change?▼

Verify each review claim against the current candidate and intended scope. Fix supported in-scope defects, explain duplicate, outdated, or out-of-scope findings, and return the changed candidate for another review pass when requested.

Does it commit changes automatically after implementation?▼

No, it does not auto-commit. Commits and publication follow the requested delivery boundary, using a publish step only when the user explicitly requests local commits or PR preparation.

What happens when required checks fail during implementation?▼

Failed required verification blocks any completion claim and ordinary delivery. Confirmed pre-existing failures are separated from introduced regressions, and their effect on confidence is recorded.

When should security remediation guidance be applied?▼

Apply the security reference only for vulnerability or sensitive-boundary changes, such as dependency remediation, code-scanning fixes, or control hardening. It is not loaded for unrelated work.