gstredny/task-manager
scaffold/.codex/skills/task-manager/SKILL.md
Manage task files in docs/tasks/open and docs/tasks/closed, including task discovery, resume/create rules, append-only Attempts logging, Left Off At updates, Code Review field handling, and needs verification closeout.
$ install --global
skillsauthnpx skillsauth add gstredny/lauren-loop task-managerInstall 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 5, 2026, 3:32 PM7.2s1 file scanned
SKILL.md
- name:
- task-manager
- description:
- Manage task files in docs/tasks/open and docs/tasks/closed, including task discovery, resume/create rules, append-only Attempts logging, Left Off At updates, Code Review field handling, and needs verification closeout.
Task Manager
Use this skill when work in this repo needs task-file discovery, creation, resume behavior, or task-file hygiene.
Start Every Task
- Check
docs/tasks/open/first for a matching task. - If a task matches, resume from
Left Off Atand avoid retrying failedAttempts. - If no task exists for substantive work, create one from
docs/tasks/TEMPLATE.mdbefore editing code.
Maintain the Task File
- Keep one task per file and use a descriptive kebab-case name.
- Keep
Attemptsappend-only. Add an entry after each meaningful code-change attempt or verification pass. - Keep
Left Off Atspecific enough that a fresh session can resume without questions. - Use the live statuses from the template:
not started,in progress,blocked,needs verification. - Add
## Code Review: completedor## Code Review: not requiredonce review status is known. Many live tasks use this field even though the template does not include it yet.
Close-Out Rules
- Only the user closes tasks.
- End implementation at
needs verification, neverdone. - Before moving a task to
docs/tasks/closed/, make sure the user has confirmed the Done Criteria and a retro entry exists indocs/tasks/RETRO.md.
Related Skills
gstredny/workflow
development
VerifiedTrustedCommunity
Follow the end-to-end delivery workflow for planning, task-file management, execution, code review, verification, and closeout without relying on Claude-specific hooks or command conventions.
1SKILL.mdUpdated Apr 5, 2026
gstredny/tdd-planning
testing
VerifiedTrustedCommunity
Plan implementation work before coding by defining public interfaces, real collaborator boundaries, and vertical RED or VERIFY slices.
1SKILL.mdUpdated Apr 5, 2026
gstredny/plan-review
data-ai
VerifiedTrustedCommunity
Review an implementation plan before execution to catch missed success criteria, scope creep, constraint violations, unverified assumptions, and missed reuse opportunities.
1SKILL.mdUpdated Apr 5, 2026
gstredny/code-review
development
VerifiedTrustedCommunity
Run code review with findings-first, severity-ordered output focused on bugs, regressions, edge cases, error handling, performance, architecture, caller impact, and missing tests.
1SKILL.mdUpdated Apr 5, 2026