skill-implementer-hard

name	skill-implementer-hard
description	Execute hard-mode implementation with anti-analysis contracts, per-phase dispatch, and territory-aware execution. Invoke for --hard implementation tasks.
allowed-tools	Agent, AskUserQuestion, Bash, Edit, Read, Write

Implementer Hard Skill

Hard-mode wrapper that delegates implementation to general-implementation-hard-agent subagent. Extends skill-implementer with:

• Single-phase dispatch context (H1): reads handoff JSON to identify next incomplete phase
• Territory parameters (H7): includes territory contract when dispatched from orchestrate-hard
• Anti-analysis contract (H2): passed in delegation context for agent enforcement

Relationship to base skill: Structurally follows skill-implementer postflight pattern. Key difference: when orchestrator_mode=true, uses per-phase dispatch (H1) rather than whole-plan dispatch. Maintenance: mirror postflight changes to this skill.

Context References

Reference (do not load eagerly):

• Path: .claude/context/formats/return-metadata-file.md - Metadata file schema
• Path: .claude/context/contracts/anti-analysis.md - H2 contract (loaded by agent)
• Path: .claude/context/contracts/wrap-up.md - H9 contract (loaded by agent)
• Path: .claude/context/contracts/territory.md - H7 contract (when territory params present)
• Path: .claude/context/patterns/postflight-control.md - Marker file protocol
• Path: .claude/context/patterns/subagent-continuation-loop.md - Continuation loop pattern

Trigger Conditions

This skill activates when:

• /implement N --hard is invoked and no extension hard variant exists
• Routed here by command-route-skill.sh with effort_flag="hard"
• skill-orchestrate-hard dispatches an implementation phase

---

Execution Flow

Stage 1: Input Validation

task_data=$(jq -r --argjson num "$task_number" \
  '.active_projects[] | select(.project_number == $num)' \
  specs/state.json)

if [ -z "$task_data" ]; then
  return error "Task $task_number not found"
fi

task_type=$(echo "$task_data" | jq -r '.task_type // "general"')
status=$(echo "$task_data" | jq -r '.status')
project_name=$(echo "$task_data" | jq -r '.project_name')
description=$(echo "$task_data" | jq -r '.description // ""')

if [ "$status" = "completed" ] || [ "$status" = "abandoned" ] || [ "$status" = "expanded" ]; then
  return error "Task is in terminal state [$status]"
fi

---

Stage 1.5: Hard-Mode Cost Note

session_flag_file="/tmp/.hard-mode-notified-${SESSION_ID:-$$}"
if [ ! -f "$session_flag_file" ]; then
  echo "[hard-mode] Hard mode active. Cost: ~3-5x standard. Use --hard for deflection-prone or formally complex tasks." >&2
  touch "$session_flag_file"
fi

---

Stage 2: Preflight Status Update

bash .claude/scripts/update-task-status.sh preflight "$task_number" implement "$session_id"

---

Stage 3: Create Postflight Marker

padded_num=$(printf "%03d" "$task_number")
mkdir -p "specs/${padded_num}_${project_name}"

cat > "specs/${padded_num}_${project_name}/.postflight-pending" << EOF
{
  "session_id": "${session_id}",
  "skill": "skill-implementer-hard",
  "task_number": ${task_number},
  "operation": "implement",
  "reason": "Hard-mode implementation in progress: per-phase dispatch, anti-analysis contract, status update pending"
}
EOF

---

Stage 3a: Calculate Artifact Number

next_num=$(jq -r --argjson num "$task_number" \
  '.active_projects[] | select(.project_number == $num) | .next_artifact_number // 1' \
  specs/state.json)

if [ "$next_num" -le 1 ]; then
  artifact_number=1
else
  artifact_number=$((next_num - 1))
fi

artifact_padded=$(printf "%02d" "$artifact_number")

---

Stage 3b: Single-Phase Dispatch Context (H1)

When orchestrator_mode=true, determine the specific phase to dispatch rather than dispatching the whole plan:

if [ "$orchestrator_mode" = "true" ]; then
  # Read handoff JSON to find next incomplete phase
  handoff_file="specs/.orchestrator-handoff.json"
  if [ -f "$handoff_file" ]; then
    phases_completed=$(jq -r '.phases_completed // 0' "$handoff_file")
    next_phase=$((phases_completed + 1))
    echo "[hard-mode] Per-phase dispatch: targeting phase ${next_phase}" >&2
  else
    next_phase=1
    echo "[hard-mode] No handoff found, dispatching phase 1" >&2
  fi
  # phase_number will be passed in delegation context
fi

---

Stage 4a: Memory Retrieval (Auto)

if [ "$clean_flag" != "true" ]; then
  memory_context=$(bash .claude/scripts/memory-retrieve.sh "$description" "$task_type" "" 2>/dev/null) || memory_context=""
fi

# Literature sub-index detection (interactive setup when sub-index is missing)
lit_context=""
if [ "$lit_flag" = "true" ] && [ ! -f "specs/literature-index.json" ]; then
  LIT_DIR="${LITERATURE_DIR:-$HOME/Projects/Literature}"
  GLOBAL_INDEX="$LIT_DIR/index.json"
  if [ ! -f "$GLOBAL_INDEX" ]; then
    # Global index missing -- inform user and continue without literature context
    echo "Note: --lit flag used but no global Literature index found at $GLOBAL_INDEX. Continuing without literature context." >&2
    # lit_context remains ""
  else
    # Global index exists but sub-index is missing -- present interactive setup options
    # (AskUserQuestion must be called inline here; cannot be delegated to a shell script)
    #
    # Present AskUserQuestion with 3 options:
    # 1. Skip: Continue without literature context
    # 2. Create setup task: Create task and continue without literature context now
    # 3. Create task and run now: Create task, populate sub-index inline, then use it
    #
    # Pseudocode (executed by Claude as the skill runs):
    #   user_choice = AskUserQuestion(
    #     "The --lit flag was used but specs/literature-index.json does not exist for this repo.\n\n" +
    #     "A global Literature index was found at $GLOBAL_INDEX.\n\n" +
    #     "How would you like to proceed?",
    #     options=[
    #       "Skip: Continue without literature context (--lit is ignored this time)",
    #       "Create setup task: Create a task to populate the sub-index, then continue without literature context",
    #       "Create task and run now: Create the task AND populate specs/literature-index.json inline before proceeding"
    #     ]
    #   )
    #
    # After user_choice:
    #   if "Skip":
    #     lit_context=""  (already set, no action needed)
    #
    #   if "Create setup task":
    #     new_task_num=$(bash .claude/scripts/literature-create-setup-task.sh)
    #     echo "Created task $new_task_num to populate specs/literature-index.json. Run /orchestrate $new_task_num to populate before using --lit."
    #     lit_context=""  (continue without literature context)
    #
    #   if "Create task and run now":
    #     new_task_num=$(bash .claude/scripts/literature-create-setup-task.sh)
    #     echo "Created task $new_task_num. Populating specs/literature-index.json inline via fork agent..."
    #     # Fork dispatch: inline population of sub-index (see Stage 4a-fork below)
    #     # After fork completes and sub-index exists:
    #     lit_context=$(bash .claude/scripts/literature-briefing.sh 2>/dev/null) || lit_context=""
    :
  fi
fi

Stage 4a-fork: Inline population (option "Create task and run now")

When the user selects "Create task and run now", after calling literature-create-setup-task.sh:

1. Invoke the Agent tool with subagent_type: "fork" and a prompt instructing the fork to:

   • Read ~/Projects/Literature/index.json (or $LITERATURE_DIR/index.json)
   • Read specs/state.json to understand this repo's task descriptions and domain
   • Analyze keyword/topic overlap between global index keywords, project_tags, and summary fields and the repo's task descriptions
   • Write matched entries to specs/literature-index.json with this schema:

     {
       "entries": [
         {"doc_id": "<id>", "relevance": "<one-sentence note>", "source": "discover"}
       ]
     }
     

   • Update the newly created task (number from step above) to completed status in specs/state.json
   • Call bash .claude/scripts/generate-todo.sh after updating state.json

2. After the fork returns, check if specs/literature-index.json was created:

   • If yes: run lit_context=$(bash .claude/scripts/literature-briefing.sh 2>/dev/null) || lit_context=""
   • If no (fork failed or timed out): log a warning, report the task number, suggest /orchestrate N, set lit_context=""

# Literature briefing injection (runs if sub-index already exists OR was just created by fork)
if [ "$lit_flag" = "true" ] && [ -f "specs/literature-index.json" ]; then
  lit_context=$(bash .claude/scripts/literature-briefing.sh 2>/dev/null) || lit_context=""
fi

Note: lit_flag is independent of clean_flag. Using --clean --lit suppresses memory retrieval but still injects literature briefing. Literature briefing is gated solely on lit_flag == "true".

---

Stage 4: Prepare Delegation Context

Pass anti-analysis contract reference and territory params (when applicable):

{
  "session_id": "{session_id}",
  "delegation_depth": 1,
  "delegation_path": ["orchestrator", "implement", "skill-implementer-hard"],
  "timeout": 7200,
  "task_context": {
    "task_number": N,
    "task_name": "{project_name}",
    "description": "{description}",
    "task_type": "{task_type}"
  },
  "artifact_number": "{artifact_number}",
  "effort_flag": "hard",
  "model_flag": "{model_flag from command}",
  "plan_path": "{plan_path}",
  "phase_number": "{next_phase when orchestrator_mode=true, null otherwise}",
  "territory": "{territory params from orchestrate-hard dispatch, null if not provided}",
  "orchestrator_mode": "{orchestrator_mode}",
  "metadata_file_path": "specs/{NNN}_{SLUG}/.return-meta.json"
}

CRITICAL: No source reading before delegation. The subagent handles all codebase exploration.

---

Stage 4b: Read Format Specification

format_content=$(cat .claude/context/formats/summary-format.md)

---

Stage 5: Invoke Subagent

Tool: Agent
Parameters:
  - subagent_type: "general-implementation-hard-agent"
  - prompt: [task_context, delegation_context, format specification, memory_context, lit_context]
  - description: "Execute hard-mode implementation for task {N} phase {next_phase}"

If lit_context is non-empty, inject it as a <literature-briefing> block after the memory context and before the task-specific instructions.

Include territory parameters in prompt when territory is non-null:

<territory-contract>
This is a hard-mode parallel dispatch. Territory rules are mandatory:
- Owned files: {territory.owned_files}
- Read-only references: {territory.read_only_files}
- See .claude/context/contracts/territory.md for full protocol
</territory-contract>

---

Stage 5b: Self-Execution Fallback

If Agent tool not used, write .return-meta.json with status: "implemented" before postflight.

---

Stage 5c: Continuation Loop Init

continuation_count=0
max_continuations=3
task_dir="specs/${padded_num}_${project_name}"
cat > "${task_dir}/.continuation-loop-guard" << EOF
{
  "session_id": "${session_id}",
  "continuation_count": 0,
  "max_continuations": 3
}
EOF

---

Postflight (ALWAYS EXECUTE)

Stage 6: Parse Subagent Return

metadata_file="specs/${padded_num}_${project_name}/.return-meta.json"

if [ -f "$metadata_file" ] && jq empty "$metadata_file" 2>/dev/null; then
    status=$(jq -r '.status' "$metadata_file")
    artifact_path=$(jq -r '.artifacts[0].path // ""' "$metadata_file")
    artifact_type=$(jq -r '.artifacts[0].type // ""' "$metadata_file")
    artifact_summary=$(jq -r '.artifacts[0].summary // ""' "$metadata_file")
    memory_candidates=$(jq -c '.memory_candidates // []' "$metadata_file")
    completion_summary=$(jq -r '.completion_data.completion_summary // ""' "$metadata_file")
    phases_completed=$(jq -r '.phases_completed // 0' "$metadata_file")
    phases_total=$(jq -r '.phases_total // 0' "$metadata_file")
else
    status="failed"
fi

---

Stage 7: Update Task Status (Postflight)

if [ "$status" = "implemented" ]; then
  bash .claude/scripts/update-task-status.sh postflight "$task_number" implement "$session_id"
fi
# On partial: keep status as "implementing" for resume

---

Stage 7a: Propagate Memory Candidates and Completion Summary

Same as skill-implementer Stage 7a + completion summary propagation.

---

Stage 8: Link Artifacts

Two-step jq pattern (Issue #1132 safety):

1. Filter out existing summary artifacts
2. Add new summary artifact

Regenerate TODO.md after linking.

---

Stage 8a: Lifecycle TTS Notification

if [ -f ".claude/scripts/lifecycle-notify.sh" ]; then
  bash .claude/scripts/lifecycle-notify.sh "$STATE_STATUS" &
fi

---

Stage 9: Cleanup

rm -f "specs/${padded_num}_${project_name}/.postflight-pending"
rm -f "specs/${padded_num}_${project_name}/.postflight-loop-guard"
rm -f "specs/${padded_num}_${project_name}/.continuation-loop-guard"
rm -f "specs/${padded_num}_${project_name}/.return-meta.json"