task-executor — for Claude Code task-executor, spec-driven-template, community, for Claude Code, ide skills, 2. Read the PRD at, tasks.md, task-reviewer, Execution, Procedures

v1.0.0
GitHub

About this Skill

Ideal for AI agents that need step 1: pre-task configuration (mandatory). task-executor is an AI agent skill for step 1: pre-task configuration (mandatory).

Features

Step 1: Pre-Task Configuration (Mandatory)
Read the task definition file at ./.spec/[feature-slug]/tasks/[num] task.md.
Read the PRD at ./.spec/[feature-slug]/prd.md for context.
Read the Tech Spec at ./.spec/[feature-slug]/techspec.md for technical requirements.
Identify dependencies from previous tasks and verify they are complete.

# Core Topics

for Claude Code 2. Read the PRD at tasks.md task-reviewer Execution Procedures
guilhermefaleiros guilhermefaleiros
[0]
[0]
Updated: 3/29/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 8/11

This page remains useful for teams, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
8/11
Quality Score
30
Canonical Locale
en
Detected Body Locale
en

Ideal for AI agents that need step 1: pre-task configuration (mandatory). task-executor is an AI agent skill for step 1: pre-task configuration (mandatory).

Core Value

task-executor helps agents step 1: pre-task configuration (mandatory). A documentation-first template for spec-driven feature delivery, covering PRDs, technical specs, task breakdowns, implementation, and review. This AI agent skill supports Claude Code, Cursor, and Windsurf workflows.

Ideal Agent Persona

Ideal for AI agents that need step 1: pre-task configuration (mandatory).

↓ Capabilities Granted for task-executor

Applying Step 1: Pre-Task Configuration (Mandatory)
Applying Read the task definition file at ./.spec/[feature-slug]/tasks/[num] task.md
Applying Read the PRD at ./.spec/[feature-slug]/prd.md for context

! Prerequisites & Limits

  • Do NOT skip any of these reads.
  • Do NOT skip any step.
  • Do not finalize the task until review issues are resolved.

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Install Path

Start With Installation And Validation

If this skill is worth continuing with, the next step is to confirm the install command, CLI write path, and environment validation.
Trusted Recheck

Cross-Check Against Trusted Picks

If you are still comparing multiple skills or vendors, go back to the trusted collection before amplifying repository noise.
Workflow

Move To Workflow Collections For Team Rollout

When the goal shifts from a single skill to team workflows, approvals, and repeatable execution, move into workflow collections.
Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is task-executor?

Ideal for AI agents that need step 1: pre-task configuration (mandatory). task-executor is an AI agent skill for step 1: pre-task configuration (mandatory).

How do I install task-executor?

Run the command: npx killer-skills add guilhermefaleiros/spec-driven-template/task-executor. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for task-executor?

Key use cases include: Applying Step 1: Pre-Task Configuration (Mandatory), Applying Read the task definition file at ./.spec/[feature-slug]/tasks/[num] task.md, Applying Read the PRD at ./.spec/[feature-slug]/prd.md for context.

Which IDEs are compatible with task-executor?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for task-executor?

Do NOT skip any of these reads.. Do NOT skip any step.. Do not finalize the task until review issues are resolved..

↓ How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add guilhermefaleiros/spec-driven-template/task-executor. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use task-executor immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

task-executor

Install task-executor, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Task Execution

Procedures

Step 1: Pre-Task Configuration (Mandatory)

  1. Read the task definition file at ./.spec/[feature-slug]/tasks/[num]_task.md.
  2. Read the PRD at ./.spec/[feature-slug]/prd.md for context.
  3. Read the Tech Spec at ./.spec/[feature-slug]/techspec.md for technical requirements.
  4. Identify dependencies from previous tasks and verify they are complete.
  5. Do NOT skip any of these reads.

Step 2: Load Required Skills

  1. Identify the technologies involved in the task (React, Hono, shadcn, etc.).
  2. Load the corresponding skills from .agents/skills/ based on technologies used.
  3. Use Context7 MCP to analyze documentation of involved languages, frameworks, and libraries.

Step 3: Task Analysis (Mandatory)

  1. Analyze the task considering:
    • Main objectives.
    • How the task fits into the project context.
    • Alignment with project rules and standards.
    • Possible approaches or solutions.
  2. Generate a task summary:
    • Task ID and Name.
    • PRD Context (main points).
    • Tech Spec Requirements (key technical requirements).
    • Dependencies.
    • Main Objectives.
    • Risks/Challenges.

Step 4: Approach Plan (Mandatory)

  1. Define a numbered step-by-step approach.
  2. Do NOT skip any step.

Step 5: Implementation (Mandatory)

  1. Begin implementation immediately after planning.
  2. Follow all project standards established in CLAUDE.md and project rules.
  3. Implement solutions without workarounds.
  4. Create and run all task tests before considering the task finished.

Step 6: Mark Task Complete (Mandatory)

  1. After successful implementation and tests, mark the task as complete in tasks.md.

Step 7: Review (Mandatory)

  1. Execute the task-reviewer agent to review the implementation.
  2. Address any issues identified by the reviewer.
  3. Do not finalize the task until review issues are resolved.

Error Handling

  • If the task file does not exist, halt and report to the user.
  • If dependencies are not complete, warn the user and ask whether to proceed.
  • If tests fail, fix the issues before marking the task as complete.
  • If the task-reviewer identifies critical issues, address them before finalizing.

Related Skills

Looking for an alternative to task-executor or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

openclaw-release-maintainer is an AI agent skill for openclaw release maintainer.

★ 333.8k
⑂ 0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

★ 149.6k
⑂ 0
AI

flags

Logo of vercel
vercel

flags is an AI agent skill for use this skill when adding or changing framework feature flags in next.js internals.

★ 138.4k
⑂ 0
Browser

pr-review

Logo of pytorch
pytorch

pr-review is an AI agent skill for pytorch pr review skill.

★ 98.6k
⑂ 0
Developer