brdohman/complete-task
.claude/skills/workflow/complete-task/SKILL.md
Steps to mark a task completed with required comments, then check parent story advancement. Enforces completion gate: implementation + testing comments required.
$ install --global
skillsauthnpx skillsauth add brdohman/agile-maestro complete-taskInstall 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 24, 2026, 8:57 PM1.8s1 file scanned
SKILL.md
- name:
- complete-task
- description:
- Steps to mark a task completed with required comments, then check parent story advancement. Enforces completion gate: implementation + testing comments required.
- disable-model-invocation:
- true
- allowed-tools:
- [TaskGet, TaskUpdate]
Task Completion
Canonical reference: Protocols 3 and 4 in
.claude/rules/global/task-state-updates.md. This skill is a quick-reference summary.
The 3 Steps
Step 1: Add implementation + testing comments
Before setting status: "completed", verify metadata.comments contains BOTH:
| Comment | type field | Required |
|---------|-------------|----------|
| What was built, files changed, local_checks verified | "implementation" | Always |
| Test file, test cases, coverage | "testing" | Unless testable: false |
If either is missing — HARD STOP. Do not set status to completed.
Step 2: Set status to completed
In a single TaskUpdate call, set status: "completed" and include both comments.
Tasks do NOT get review_stage or review_result — only Stories and Epics use those fields.
Step 3: Check parent story advancement
After completing a task:
- Call
TaskGeton the parent story - Check if ALL sibling tasks are
status: "completed" - If yes — submit the story for code review: set
review_stage: "code-review",review_result: "awaiting", add a"handoff"comment
See Also
- Protocol 3 (complete with comments):
.claude/rules/global/task-state-updates.md - Protocol 4 (parent advancement):
.claude/rules/global/task-state-updates.md - Comment format and field reference: skill
agent-shared-context
Related Skills
brdohman/xctest-patterns
testing
VerifiedTrustedCommunity
XCTest patterns for macOS Swift apps. Unit tests, async tests, Core Data tests, mock patterns, and assertion reference. Use when writing or reviewing tests.
2SKILL.mdUpdated Apr 16, 2026
brdohman/workflow-state
tools
VerifiedTrustedCommunity
How to transition workflow state between review stages. Rules for setting review_stage and review_result fields on Stories and Epics.
2SKILL.mdUpdated Apr 16, 2026
brdohman/workflow-comments
documentation
VerifiedTrustedCommunity
Comment structure and rules for task workflow updates. Use when adding any comment to a task during implementation, review, or fix cycles.
2SKILL.mdUpdated Apr 16, 2026
brdohman/validate-task
testing
VerifiedTrustedCommunity
Validate task/story/epic/bug/techdebt metadata against schema v2.0. Run after TaskCreate or TaskUpdate to verify compliance. Returns pass/fail with actionable details.
2SKILL.mdUpdated Apr 16, 2026