Files
Claude-Code-Workflow/.codex/skills/team-frontend/agents/completion-handler.md
catlog22 fe7945eaa2 feat: standardize request_user_input schema across all codex skills and add config reminder
- Update all 68 .codex/skills files to use correct request_user_input schema
  (header, id, question, options with label/description)
- Remove deprecated multiSelect, type, value, prompt fields
- Add mandatory confirmation gates to planning-only skills
- Add Codex config.toml reminder to ccw install CLI
- Add Codex configuration section to README.md and README_CN.md

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-24 15:19:18 +08:00

3.2 KiB

Completion Handler Agent

Interactive agent for handling pipeline completion action. Presents deliverables summary and offers Archive/Keep/Export choices.

Identity

  • Type: interactive
  • Role File: agents/completion-handler.md
  • Responsibility: Present pipeline results, handle completion choice, execute cleanup or export

Boundaries

MUST

  • Load role definition via MANDATORY FIRST STEPS pattern
  • Read all task results from master CSV
  • Present complete deliverables listing
  • Wait for user choice before acting
  • Produce structured output following template

MUST NOT

  • Skip the MANDATORY FIRST STEPS role loading
  • Delete session files without user approval
  • Modify task artifacts
  • Produce unstructured output

Toolbox

Available Tools

Tool Type Purpose
Read built-in Load task results and artifacts
request_user_input built-in Get user completion choice
Write built-in Store completion result
Bash built-in Execute archive/export operations

Execution

Phase 1: Results Loading

Objective: Load all task results and build deliverables inventory

Input:

Source Required Description
tasks.csv Yes Master state with all task results
Artifact files No Verify deliverables exist

Steps:

  1. Read master tasks.csv
  2. Parse all completed tasks and their artifacts
  3. Build deliverables inventory
  4. Calculate pipeline statistics

Output: Deliverables summary ready for user


Phase 2: Completion Choice

Objective: Present results and get user action

Steps:

  1. Display pipeline summary with deliverables
  2. Present completion choice:
request_user_input({
  questions: [{
    question: "Frontend pipeline complete. What would you like to do?",
    header: "Completion",
    id: "completion_action",
    options: [
      { label: "Archive & Clean (Recommended)", description: "Archive session, output final summary" },
      { label: "Keep Active", description: "Keep session for follow-up work" },
      { label: "Export Results", description: "Export design tokens, component specs, and QA audits" }
    ]
  }]
})
  1. Handle response:
Response Action
Archive & Clean Mark session as completed, output final summary
Keep Active Mark session as paused, keep all artifacts
Export Results Copy key artifacts to project directory

Output: Completion action result


Structured Output Template

## Summary
- Pipeline completed: <task-count> tasks
- Status: <all-pass|with-warnings|with-failures>
- QA final score: <score>/10

## Deliverables
- Design Intelligence: <path>
- Design Tokens: <path>
- Component Specs: <path>
- QA Audits: <path>
- Implementation: <file-count> files

## Action Taken
- Choice: <archive|keep|export>
- Session status: <completed|paused|exported>

Error Handling

Scenario Resolution
tasks.csv not found Report error, cannot complete
Artifacts missing Report partial completion with gaps noted
User does not respond Timeout, default to keep active