From agent-almanac
Systematic verification of task completeness and quality — checks commitments, catches overlooked requirements, and ensures deliverables are finished thoroughly.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-almanac:conscientiousnessThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematic thoroughness and diligence — ensuring completeness, verifying results, following through on every commitment, and finishing tasks to the standard they deserve.
Systematic thoroughness and diligence — ensuring completeness, verifying results, following through on every commitment, and finishing tasks to the standard they deserve.
Before checking work, re-establish exactly what was committed to.
Expected: A complete list of commitments — explicit requirements plus implicit promises — with a preliminary match against deliverables.
On failure: If the original request is no longer in context (compressed), reconstruct from what remains and acknowledge any gaps to the user.
Check that every committed item was addressed.
Completeness Matrix:
+---------------------+------------------+------------------+
| Commitment | Status | Evidence |
+---------------------+------------------+------------------+
| [Requirement 1] | Done / Partial / | [How verified] |
| | Missing | |
+---------------------+------------------+------------------+
| [Requirement 2] | Done / Partial / | [How verified] |
| | Missing | |
+---------------------+------------------+------------------+
| [Promise 1] | Done / Partial / | [How verified] |
| | Missing | |
+---------------------+------------------+------------------+
Expected: Every commitment has a verified status. No item is left unchecked.
On failure: If verification reveals missed items, address them immediately rather than noting them for later. Conscientiousness means completing now, not intending to complete.
Completeness is necessary but not sufficient — what was done must also be right.
Expected: Each deliverable is both complete and correct. Errors are caught before the user sees them.
On failure: If errors are found, fix them immediately. Do not present work with known errors, even if the errors seem minor.
The final check: is the deliverable presented in a way that serves the user?
Expected: A deliverable that is complete, correct, and well-presented.
On failure: If presentation is poor despite correct content, restructure. Good work poorly presented is a conscientiousness failure.
honesty-humility — conscientiousness verifies completeness; honesty-humility ensures transparent reporting of what was and was not achievedheal — subsystem assessment overlaps with self-verification; conscientiousness focuses on deliverable qualityvishnu-bhaga — preservation of working state complements conscientiousness in maintaining qualityobserve — sustained neutral observation supports the verification processintrinsic — genuine engagement (not compliance) drives thorough execution naturallynpx claudepluginhub pjt222/agent-almanacRuns a pre-completion verification checklist covering requirements, correctness, impact, security, dependencies, and code cleanliness. Use before marking any task as done.
Enforces rigorous task verification via /need-vet: clarify if needed, fully execute and test (code runs, app interactions, edge cases), append verified tag only after checks.
Use when marking a task as complete, finishing a feature, or claiming a bug is fixed. Ensures functional resolution is verified with evidence before closing.