name: plan-mode-tasks description: Create and maintain agents/tasks/task-name/plan.md and tasks.md for Plan Mode plans.

Plan Mode Tasks

Delegation Model

• Route plan artifact creation and maintenance through registered plan_mode_tasks subagent instead of keeping workflow only in parent thread.
• Invoke plan_mode_tasks after Plan Mode plan is approved and task needs plan.md and tasks.md created or updated.
• Reuse same plan_mode_tasks subagent for rest of turn's plan artifact work so approved plan state stays in one place.
• Configure subagent through agents/plan-mode-tasks.toml and agents/plan-mode-tasks.md, with model selection kept in agent config.
• Keep actual implementation work in parent thread or appropriate workflow subagent; use plan_mode_tasks only for plan artifacts themselves.

Intent

• Create plan artifacts in directory user requests; default to ./.agents/tasks/<task>/ whenever Plan Mode plan is produced.

Permission Gate

• You have full create/edit permission for plan and task docs.
• If approval is denied, provide planned contents in chat only.

Task Slugging

• Derive <task> from user's task title or primary request text.
• Transform to lowercase.
• Replace whitespace with hyphens.
• Remove non-alphanumeric characters except hyphens.
• Trim leading and trailing hyphens.
• If no clear task title exists, ask user for short task name before proceeding.
• For plans involving code changes, follow workflow-code for guidance.

Files

plan.md

Use this template and fill it with final plan content.

# Goal

# Scope

# Non-goals

# Constraints

# Plan

# Risks

# Tests

tasks.md

• Use checkbox list format.
• Seed tasks from Plan steps, one task per line.
• Use this format:

- [ ] Task description

Updates

• If plan changes, ask for approval again before updating plan.md or tasks.md.
• Keep tasks.md aligned to current Plan steps.

Collisions

• If ./.agents/tasks/<task>/ already exists, reuse it and update plan.md and tasks.md.