# 1. Detect project type from manifest files
ls -la *.json *.toml *.mod *.lock *.yaml *.yml 2>/dev/null | head -10

# 2. Read manifest to identify dependencies and scripts
cat package.json 2>/dev/null || cat go.mod 2>/dev/null || cat Cargo.toml 2>/dev/null || cat pyproject.toml 2>/dev/null

# 3. Find test framework from config or existing tests
grep -r "test" --include="*.json" --include="*.toml" -l 2>/dev/null | head -3
fd '_test\.' --type f | head -3   # Go/Rust pattern
fd '\.test\.' --type f | head -3  # JS/TS pattern
fd 'test_' --type f | head -3     # Python pattern

# 4. Learn commit style from recent history
git log --oneline -5

# 5. Discover code quality tools
cat .eslintrc* .prettierrc* rustfmt.toml .golangci.yml pyproject.toml 2>/dev/null | head -20

fd '\.md$' ~/.claude/agents --type f     # Available agents
ls -la                                    # Codebase structure
cat {manifest_file}                       # From project_context
ls <expected/path> 2>/dev/null            # Verify paths exist
grep -r "pattern" src/ lib/ internal/     # Find existing implementations

# Comment block at top of plan:
# PRODUCERS: Task 4 → ExtractMetrics, Task 5 → LoadSession
# CONSUMERS: Task 16 → [4, 5, 15]
# VALIDATION: All consumers depend_on producers ✓

# YAML field (validated by Conductor):
data_flow_registry:
  producers:
    FunctionName:
      - task: 4
        description: "Creates this function"
  consumers:
    FunctionName:
      - task: 16
        description: "Uses this function"

implementation:
  approach: |
    Strategy and architectural decisions.
  key_points:
    - point: "EnforceModuleIsolation with git diff"
      details: "Compare modified files against task.Files"
      reference: "src/executor/module_guard.ts"  # Use project's actual paths

# Derived using SAME terminology:
success_criteria:
  - "EnforceModuleIsolation runs git diff, compares against task.Files"

conductor:
  default_agent: general-purpose
  worktree_groups:
    - group_id: "name"
      tasks: [1, 2, 3]
      rationale: "Why grouped"

planner_compliance:
  planner_version: "5.0.0"
  strict_enforcement: true
  required_features: [dependency_checks, test_commands, success_criteria, data_flow_registry, package_guard]

data_flow_registry:
  producers: {}
  consumers: {}

plan:
  metadata:
    feature_name: "Name"
    created: "YYYY-MM-DD"
    target: "Goal"
  context:
    framework: "{language}"           # From project_context
    test_framework: "{test_command}"  # From project_context
  tasks: []

- task_number: "1"
  name: "Task name"
  agent: "agent-name"
  files: ["src/path/to/file.ext"]     # Use project's actual structure
  depends_on: []

  success_criteria:
    - "Criterion from key_point 1"
    - "No TODO/placeholder/unused patterns"

  test_commands:
    - "{test_command} {test_path}"    # From project_context

  runtime_metadata:
    dependency_checks:
      - command: "{build_command}"    # From project_context
        description: "Verify build"
    documentation_targets: []

  description: |
    <dependency_verification priority="execute_first">
      <commands># verify deps</commands>
    </dependency_verification>
    <task_description>What to implement.</task_description>

  implementation:
    approach: |
      Strategy.
    key_points:
      - point: "Name"
        details: "What and why"
        reference: "file.ext"

  code_quality:
    pipeline:
      command: "{format_command} && {test_command}"  # From project_context
      exit_on_failure: true

  commit:
    type: "feat"
    message: "description"
    files: ["path/**"]

depends_on:
  - 4                                    # Same file
  - file: "plan-01-foundation.yaml"      # Different file
    task: 2

- task_number: "N"
  type: integration
  success_criteria: [...]      # Component-level
  integration_criteria: [...]  # Cross-component

□ Every key_point has corresponding success criterion (same terms)
□ Every success criterion traces to a key_point
□ Data flow: consumers depend_on all producers
□ Module conflicts serialized via depends_on
□ All file paths verified to exist (or will be created)
□ Integration tasks have both success_criteria AND integration_criteria
□ Every task has: implementation, success_criteria, test_commands, runtime_metadata

conductor validate docs/plans/<plan>.yaml

□ planner_compliance.required_features = [dependency_checks, test_commands, success_criteria, data_flow_registry, package_guard]
□ conductor.worktree_groups defined with group_id, tasks, rationale
□ data_flow_registry.producers lists all cross-task data creators
□ data_flow_registry.consumers lists all cross-task data users
□ Every task has commit section with type, message, files
□ Every task has code_quality section with project-appropriate commands
□ plan.metadata has feature_name, created, target
□ plan.context has framework, test_framework (matching project_context)