exfig: Command for Claude Code

Task Planning with Dependencies

Purpose: Analyze a task and break it down into subtasks with explicit dependencies, enabling parallel execution where possible.

Output Format (TOON-like)

Generate plan in this structured format:

command:
  name: plan-<task-slug>
  purpose: <task description>
  version: 1.0

tasks[N]{id,title,description,depends_on,parallel_group,type}:
  <id>,<title>,<description>,[deps],[group],[type]
  ...

execution_order:
  phase_1:
    parallel: [task_ids that can run in parallel]
  phase_2:
    sequential: [task_id] # build/test tasks
  phase_3:
    parallel: [task_ids for fixes if needed]
  ...

dependency_graph:
  <task_id>: [list of task_ids this depends on]
  ...

Task Types

• analysis - Code analysis, research, reading
• implementation - Writing new code
• modification - Changing existing code
• build - Building project/module
• test - Running tests
• fix - Fixing issues found by build/tests
• review - Code review, validation

Dependency Rules

Critical Rules for Parallel Execution

1. Independent tasks (no shared files/modules) can run in parallel
2. Build tasks MUST wait for ALL parallel implementation tasks to complete
3. Test tasks MUST wait for build to succeed
4. Fix tasks MUST wait for test results
5. Tasks modifying same file MUST be sequential

Dependency Detection

• Same file modification → sequential
• Same module modification → sequential (unless different files)
• Different modules → parallel possible
• Build depends on → all implementation tasks
• Test depends on → successful build
• Fix depends on → test results

Instructions

1. Analyze the task:

   • Read relevant code files mentioned in task
   • Identify affected modules/files
   • Detect potential conflicts

2. Break down into subtasks:

   • Create atomic, independent subtasks where possible
   • Identify dependencies between subtasks
   • Group parallelizable tasks

3. Generate execution plan: