Install
$ agentstack add skill-pavel-molyanov-molyanov-ai-dev-claude-command-do-task ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Converted Command Workflow: do-task
Generated from ~/.claude/commands/do-task.md. Treat Claude-only tool names as conceptual workflow steps and use available Codex tools/policies.
Codex Policy Gates
- Ask before external actions such as GitHub repository creation,
git push, deploys, or sending messages unless the user explicitly requested that exact action. - Deployments must go through GitHub CI/CD; direct server access is only for emergency debugging of broken production.
- Never ask the user to paste secrets in chat. Direct them to
.envfiles or GitHub Actions secrets.
Do Task
Project Documentation Autosync
If this command changes any project-local .claude/** file, immediately run:
~/.claude/scripts/sync-to-codex.sh --project "$PWD" --apply
If sync reports a conflict, stop and report it. Include generated .codex/** changes in the same commit as the .claude/** source change.
Execute a spec-driven task with validation and status tracking.
Step 1: Read Task
- Read task file (user provides path or task number)
- If user didn't specify → ask: "Which task to execute?"
- Derive feature directory from task path:
work/{feature}/tasks/N.md→work/{feature}/
All logs/ paths in the task (Reviewers section, What to do, Acceptance Criteria) are relative to this feature directory. Resolve them as {feature_dir}/logs/... when creating files.
- Verify task status is
planned(if not → ask user before proceeding) - Update task frontmatter:
status: planned→status: in_progress - Read every file listed in the task's "Context Files" section
Step 2: Execute
- Load each skill listed in the task (frontmatter
skills: [...]and "Required Skills" section)
- If a skill is not found → warn user, continue with remaining skills
- If task has no skill (frontmatter
skills: []or absent) → read the task, execute "What to do" and "Verification Steps" directly. For tasks with user instructions → show the instruction to user, wait for confirmation.
- Follow loaded skill workflow
- Git commit implementation (code + tests pass):
feat|fix|refactor: task {N} — {brief description} - For each reviewer from the task's "Reviewers" section (if present):
- Spawn subagent via spawnagent (subagenttype = reviewer name, e.g.
code-reviewer) - Pass: git diff of changes, path to task file, path to tech-spec, path to user-spec
- Reviewer loads its own skill automatically (via agent frontmatter
skills:) - Report is written to the path specified in the task's "Reviewers" section, resolved relative to the feature directory (e.g.,
logs/working/task-1/...→{feature_dir}/logs/working/task-1/...) - Read report. If findings exist → fix, re-run tests, git commit:
fix: address review round {N} for task {N}, repeat (max 3 rounds)
Step 3: Verify
- Check each acceptance criterion from task file
- If task has "Verification Steps → Smoke" → execute each smoke command, record results in decisions.md Verification section
- If task has "Verification Steps → User" → ask user to verify, wait for confirmation
- If any verification fails → fix → re-run tests → re-run reviewers (new round) → re-verify
- After 3 failed rounds → stop, report failures to user, keep status
in_progress - Tool unavailable → document, suggest manual check
Step 4: Complete
- Read template
~/.claude/shared/work-templates/decisions.md.templateand write a concise execution report towork/{feature}/decisions.md. Follow template format strictly — no extra sections. - Update task frontmatter:
status: in_progress→status: done - Update tech-spec:
- [ ] Task N→- [x] Task N - Git commit:
chore: complete task {N} — update status and decisions
Self-Verification
- [ ] Task status is
done - [ ] Tech-spec checkbox updated
- [ ] decisions.md entry written with reviews and verification results
- [ ] Git commit created with task reference
- [ ] Every acceptance criterion from task file is met
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: pavel-molyanov
- Source: pavel-molyanov/molyanov-ai-dev
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.