maestria-co/task-plan-phase-completion
skills/task-plan-phase-completion/SKILL.md
Load after the primary concern skill's work is done, to close any task. Covers code review, context updates, retrospective, and completion summary.
development
Updated Apr 26, 2026
$ install --global
skillsauthnpx skillsauth add maestria-co/ai-playbook task-plan-phase-completionInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 26, 2026, 6:39 AM52.3s1 file scanned
SKILL.md
- name:
- task-plan-phase-completion
- description:
- Load after the primary concern skill's work is done, to close any task. Covers code review, context updates, retrospective, and completion summary.
- user-invocable:
- false
Phase: Completion
Load this skill following primary concern skill finalization — for any task category. It addresses universal closure operations: code audit, context refresh, retrospective, and completion summary. Sustain minimalism in this skill. It loads at every task terminus; token expenditure is consequential.
@reviewer Delegation Structure
Feature: [characterization]
All altered files:
- [file/path]: [alteration characterization]
Relevant standards: [.context/standards/ citations]
Audit focus: [particular concern — security perimeter, performance pathway, etc.]
Remediate all critical and moderate conclusions. Archive minor conclusions in plan.md ## Open Questions / Blockers for subsequent attention.
Context Update Checklist
Post-audit and pre-closure, evaluate each element:
- [ ] Domain files: Did this task expose novel behaviors, entities, or business rules in any domain? If affirmative, refresh
.context/domains/[domain].md. - [ ] Architecture files: Did this task introduce or alter a pattern? If affirmative, refresh
.context/architecture/patterns.md. - [ ] Standards files: Did this task establish new conventions? If affirmative, refresh pertinent
.context/standards/files. - [ ] Testing files: Did this task reveal novel test patterns? If affirmative, refresh
.context/testing/. - [ ] decisions: Did this task produce significant architectural determinations not yet archived? If affirmative, append to
.context/decisions/. - [ ] copilot-instructions.md: Refresh EXCLUSIVELY for project-spanning alterations (new toolchain elements, command alterations, high-level convention shifts). AVOID region-specific detail here.
Load context-maintenance when refresh footprint is extensive (multiple files across multiple regions).
Retrospective
Load task-retrospective skill for comprehensive retrospective execution.
Minimally, address these three queries:
- What error or friction surfaced that merits future avoidance?
- What pattern or methodology succeeded that merits repetition?
- What
.context/updates emerge from this experience?
Archive conclusions in .context/retrospectives/ (rolling archive, sustain last 10–15 entries). Promote each lesson to appropriate .context/ subdirectory.
Completion Summary
## Completion Summary
**Accomplished:** [1–2 sentence synopsis]
**Files altered:** [tally and notable paths]
**Tests:** [quantity appended, pass/fail status]
**Next effort:** [technical debt or next tasks, or "none"]
Skill Interdependencies
task-retrospective: Load for comprehensive retrospective execution.context-maintenance: Load when context refreshes span extensively (multiple files across multiple regions).commit-discipline: Load for terminal commit of closure files, retrospective entries, and context updates.task-plan-phase-testing: If tests remain incomplete, load that skill before executing completion.
Excluded scope: investigation, architectural audit, implementation orchestration, test delegation.
Related Skills
maestria-co/writing-tests
development
VerifiedTrustedCommunity
Writes and runs a test suite for a piece of code, covering happy path, edge cases, error cases, and security cases. Use when: implementation is complete and needs test coverage, a bug needs a reproduction test and fix validation, or code needs coverage before a refactor. Do not use when: the code under test is not yet implemented, or the spec is still unclear.
SKILL.mdUpdated Apr 26, 2026
maestria-co/writing-skills
testing
VerifiedTrustedCommunity
Use when creating a new skill, editing an existing skill, or helping a user author a skill for this system. Covers structure, discoverability, quality, and discipline hardening.
SKILL.mdUpdated Apr 26, 2026
maestria-co/verification-checklist
development
VerifiedTrustedCommunity
Evidence-based verification process to run before marking any task complete. Use this skill every time you're about to report that work is done — for features, bug fixes, refactoring, or any code change. This catches the most common failure mode: declaring "done" without proof. If you're finishing up and about to tell the user the task is complete, run this checklist first.
SKILL.mdUpdated Apr 26, 2026
maestria-co/using-skills
development
VerifiedTrustedCommunity
Teaches agents how to discover, select, and invoke skills from the skill library. Use this skill whenever you're uncertain which skill applies to a task, when composing multiple skills for complex work, or when you need to understand what skills are available. This is your go-to when facing an ambiguous task and need to figure out the right approach before diving into implementation.
SKILL.mdUpdated Apr 26, 2026