AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Claude Command Do Task

skill-pavel-molyanov-molyanov-ai-dev-claude-command-do-task · by pavel-molyanov

Converted Codex workflow from Claude slash command `do-task`. Use when the user asks to run the equivalent command or describes this workflow.

No reviews yet
0 installs
7 views
0.0% view→install

Install

$ agentstack add skill-pavel-molyanov-molyanov-ai-dev-claude-command-do-task

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No 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.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-pavel-molyanov-molyanov-ai-dev-claude-command-do-task)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
1mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

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 →
Are you the author of Claude Command Do Task? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

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 .env files 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

  1. Read task file (user provides path or task number)
  • If user didn't specify → ask: "Which task to execute?"
  1. Derive feature directory from task path: work/{feature}/tasks/N.mdwork/{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.

  1. Verify task status is planned (if not → ask user before proceeding)
  2. Update task frontmatter: status: plannedstatus: in_progress
  3. Read every file listed in the task's "Context Files" section

Step 2: Execute

  1. 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.
  1. Follow loaded skill workflow
  2. Git commit implementation (code + tests pass): feat|fix|refactor: task {N} — {brief description}
  3. For each reviewer from the task's "Reviewers" section (if present):
  4. Spawn subagent via spawnagent (subagenttype = reviewer name, e.g. code-reviewer)
  5. Pass: git diff of changes, path to task file, path to tech-spec, path to user-spec
  6. Reviewer loads its own skill automatically (via agent frontmatter skills:)
  7. 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/...)
  8. 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

  1. Check each acceptance criterion from task file
  2. If task has "Verification Steps → Smoke" → execute each smoke command, record results in decisions.md Verification section
  3. If task has "Verification Steps → User" → ask user to verify, wait for confirmation
  4. 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

  1. Read template ~/.claude/shared/work-templates/decisions.md.template and write a concise execution report to work/{feature}/decisions.md. Follow template format strictly — no extra sections.
  2. Update task frontmatter: status: in_progressstatus: done
  3. Update tech-spec: - [ ] Task N- [x] Task N
  4. 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.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.