/task - Task Management Command

Manage tasks within CODITECT features. Tasks are the actionable work items that developers complete.

Track Assignment

IMPORTANT: Before creating any task, search the MASTER-TRACK-INDEX.md to ensure correct track assignment.

# Search for matching track by keywords in your task
grep -i "keyword" internal/project/plans/tracks/MASTER-TRACK-INDEX.md

Track System: 37 tracks (A-N Technical, O-AA PCF Business, AB-AK Extensions)

Usage

# Create task in feature
/task create F001 "Task Title" [--hours 4] [--assignee "name"]

# List tasks
/task list [F001] [--status STATUS] [--assignee "name"] [--mine]

# Show task details
/task show T0001

# Start working on task
/task start T0001

# Complete task
/task complete T0001 [--hours 3.5]

# Block task
/task block T0001 --reason "Waiting for API access"

# Add subtask
/task add-subtask T0001 "Subtask Title"

# Log hours
/task log T0001 --hours 2.5

# Link session to task
/task link-session T0001

System Prompt

System Prompt

⚠️ EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

1. IMMEDIATELY execute - no questions, no explanations first
2. ALWAYS show full output from script/tool execution
3. ALWAYS provide summary after execution completes

DO NOT:

• Say "I don't need to take action" - you ALWAYS execute when invoked
• Ask for confirmation unless requires_confirmation: true in frontmatter
• Skip execution even if it seems redundant - run it anyway

The user invoking the command IS the confirmation.

---

You are managing CODITECT tasks using the Work Item Hierarchy system (ADR-006).

ID Convention:

• Tasks: T{NNNN} (T0001, T0042, T1234)
• Subtasks: ST{NNNN} (child of task)

Hierarchy: Project → Sub-Project → Epic → Feature → Task → Subtask

Status Workflow:

backlog → planned → in_progress → review → completed
                  ↓
               blocked

Available Actions:

Create Task

python3 scripts/work_items.py task create "$FEATURE_ID" "$TITLE" \
  --hours $ESTIMATE --assignee "$ASSIGNEE"

Start Task (set in_progress)

python3 scripts/work_items.py task start "$TASK_ID"

Complete Task

python3 scripts/work_items.py task complete "$TASK_ID" --actual-hours $HOURS

Block Task

python3 scripts/work_items.py task block "$TASK_ID" --reason "$REASON"

Log Hours

python3 scripts/work_items.py task log "$TASK_ID" --hours $HOURS

Link Session

python3 scripts/work_items.py task link-session "$TASK_ID" "$SESSION_ID"

Output Format:

Task T0001 created successfully.

  ID:          T0001
  Title:       Implement login form validation
  Feature:     F001 (User Login Flow)
  Status:      backlog
  Assignee:    -
  Estimate:    4h
  Actual:      0h
  Subtasks:    0
  Created:     2025-12-13T10:30:00Z

Next steps:
  /task start T0001              - Begin work
  /task add-subtask T0001 "..."  - Break down further
  /task link-session T0001       - Link current session

Examples

Quick Task Workflow

# Create task
/task create F001 "Write unit tests" --hours 3

# Start working
/task start T0001

# Link this session
/task link-session T0001

# Log progress
/task log T0001 --hours 1.5

# Complete
/task complete T0001 --hours 2.5

View Task with Subtasks

/task show T0001

Output:

T0001: Implement OAuth flow (in_progress)
  Feature:  F001 (OAuth Integration)
  Status:   in_progress (started 2h ago)
  Assignee: developer@example.com
  Hours:    4h estimated, 2h logged
  Sessions: 2 linked

  Subtasks:
  ├── ST0001: Configure OAuth client (100%) ✓
  ├── ST0002: Handle callback URL (100%) ✓
  ├── ST0003: Store tokens securely (50%)
  └── ST0004: Test error handling (0%)

  Linked Sessions:
  - 81c31763... (2025-12-13, 1.5h)
  - 5f123d77... (2025-12-13, 0.5h)

My Tasks

/task list --mine --status in_progress

Blocked Tasks Report

/task list --status blocked

Output:

Blocked Tasks:
T0042: Deploy to staging
  Blocked: Waiting for DevOps approval
  Blocked since: 2 days ago

T0089: Integrate payment API
  Blocked: API credentials not received
  Blocked since: 1 day ago

---

Action Policy

<default_behavior> This command implements changes by default when user intent is clear. Proceeds with:

• Task creation and updates
• Status transitions
• Hour logging
• Session linking

Provides concise progress updates during execution. </default_behavior>

After execution, verify: - Task created/updated successfully - Status reflects correct state - Hours logged accurately - Session linked if requested

Success Output

When task operation completes:

✅ COMMAND COMPLETE: /task
Action: <create|start|complete|block>
Task: T<NNNN>
Status: <status>
Feature: F<NNN>
Hours: X estimated, Y logged

Completion Checklist

Before marking complete:

• Task operation executed
• Status updated correctly
• Output displayed
• Next steps provided

Failure Indicators

This command has FAILED if:

• ❌ Feature not found
• ❌ Task not found
• ❌ Invalid status transition
• ❌ Script execution error

When NOT to Use

Do NOT use when:

• Managing features (use /feature)
• Managing projects (use /project)
• Sprint planning (use /sprint)

Anti-Patterns (Avoid)

Anti-Pattern	Problem	Solution
Skip hour logging	No tracking	Log hours regularly
Ignore blockers	Tasks stuck	Use /task block with reason
Orphan tasks	No session link	Use /task link-session

Principles

This command embodies:

• #3 Complete Execution - Full task lifecycle
• #9 Based on Facts - Actual hours tracked

Full Standard: CODITECT-STANDARD-AUTOMATION.md

---

Script: scripts/work_items.py Standard: CODITECT-CORE-STANDARDS/CODITECT-STANDARD-WORK-ITEMS.md Version: 1.0.0