cuioss/task-standalone

Task Implementation Skill

Implement tasks through goal-based workflow with automatic mode selection and verification.

Enforcement

Execution mode: Auto-detect mode (FULL/PLAN/QUICK) from input, execute workflow, verify build, commit.

Prohibited actions:

• Never push to remote unless push parameter is explicitly set
• Never skip build verification after implementation
• Do not discard pending workflow state without user confirmation

Constraints:

• Memory cleanup must happen after workflow completion (handoffs category)
• Build verification iterates up to 3 times on failure before stopping
• All user interactions use AskUserQuestion tool with proper YAML structure
• Each workflow step that performs a script operation has an explicit bash code block with the full python3 .plan/execute-script.py command

Parameters

| Parameter | Type | Description | |-----------|------|-------------| | task | required | GitHub issue number/URL or task description | | language | optional | java|javascript (auto-detects if not specified) | | quick | optional | Skip review/plan, execute directly (default: false) | | push | optional | Auto-push after successful implementation (default: false) | | handoff | optional | Handoff structure from previous task (JSON) |

Prerequisites

Load required skills:

Skill: plan-marshall:manage-memories

Workflow

Step 1: Process Handoff Input

If handoff parameter provided: Parse JSON, extract artifacts/decisions/constraints, load memory refs.

Step 2: Determine Mode

If task matches /^\d+$/ or "github.com/*/issues/" → FULL mode (Review → Plan → Execute)
If quick=true → QUICK mode (Execute only)
Otherwise → PLAN mode (Plan → Execute)

Step 3: Check Memory for Pending Workflow

python3 .plan/execute-script.py plan-marshall:manage-memories:manage-memory list --category handoffs

If pending found, present using AskUserQuestion:

AskUserQuestion:
  questions:
    - question: "A pending workflow was found. How would you like to proceed?"
      header: "Pending"
      options:
        - label: "Resume"
          description: "Continue from where the previous workflow left off"
        - label: "Start fresh"
          description: "Discard pending state and start a new workflow"
        - label: "Abort"
          description: "Cancel task implementation"
      multiSelect: false

Step 4: Execute Mode-Specific Workflow

FULL: Load issue (via tools-integration-ci:issue-view), Review requirements, Plan implementation, Execute tasks, save progress to memory.

PLAN: Plan implementation, Execute tasks, save progress to memory.

QUICK: Execute task directly.

Step 5: Verify Implementation

Auto-detect language: pom.xml → Java, package.json → JavaScript

Run build verification. Iterate up to 3 times if fails.

Step 6: Commit and Push

If verification succeeds: Commit via git workflow.

If push=true: Run git push.

Step 7: Cleanup and Return

Cleanup memory:

python3 .plan/execute-script.py plan-marshall:manage-memories:manage-memory cleanup --category handoffs --pattern "workflow-*"

---

Mode Details

FULL Mode (GitHub Issue)

1. Load issue details from GitHub
2. Review: Analyze requirements, identify acceptance criteria
3. Plan: Break down into implementation steps
4. Execute: Implement each step
5. Verify: Run build/tests

PLAN Mode (Task Description)

1. Plan: Analyze task, create implementation steps
2. Execute: Implement each step
3. Verify: Run build/tests

QUICK Mode

1. Execute: Implement task directly without planning
2. Verify: Run build/tests

---

Usage Examples

Full workflow with GitHub issue:

/task-standalone task=123

Quick execution (no planning):

/task-standalone task="Add validation to User.java" quick

Java task with auto-push:

/task-standalone task=456 language=java push

Task description with planning:

/task-standalone task="Implement user authentication service"

Architecture

Delegates to skills:

/task-standalone (orchestrator)
  ├─> manage-memories skill (state persistence)
  └─> workflow-integration-git skill (commit workflow)

Continuous Improvement

If you discover issues or improvements during execution, record them:

1. Activate skill: Skill: plan-marshall:manage-lessons
2. Record lesson with component: {type: "skill", name: "task-standalone", bundle: "plan-marshall"}

Related

| Skill | Purpose | |-------|---------| | plan-marshall:manage-memories | State persistence for recovery | | plan-marshall:workflow-integration-git | Git commit workflow | | plan-marshall:workflow-pr-doctor | Fix PR issues after implementation |