Plan

Step 2: Resolve Task Directory

If .trellis/.current-task exists, use it as TASK_DIR. Otherwise create one:

TASK_DIR=$(uv run ./.trellis/scripts/task.py create "<title>" --slug <task-slug>)
uv run ./.trellis/scripts/task.py start "$TASK_DIR"

Step 3: Initialize and Prime Context

uv run ./.trellis/scripts/task.py init-context "$TASK_DIR" <backend|frontend|fullstack>
uv run ./.trellis/scripts/task.py ensure-artifacts "$TASK_DIR"
uv run ./.trellis/scripts/task.py constitution-check "$TASK_DIR"

Add focused context entries:

uv run ./.trellis/scripts/task.py add-context "$TASK_DIR" implement "<path>" "<reason>"
uv run ./.trellis/scripts/task.py add-context "$TASK_DIR" check "<path>" "<reason>"
uv run ./.trellis/scripts/task.py add-context "$TASK_DIR" debug "<path>" "<reason>"

Prefer existing implementation patterns, relevant specs under .trellis/spec/, and nearby tests.

Step 4: Write prd.md

Create or update $TASK_DIR/prd.md with:

• Goal and scope
• Explicit requirements
• Acceptance criteria checklist
• Technical notes and constraints
• Out-of-scope items

Keep requirements specific and verifiable.

Step 5: Configure Metadata and Validate

uv run ./.trellis/scripts/task.py set-branch "$TASK_DIR" "feature/<task-slug>"
uv run ./.trellis/scripts/task.py set-scope "$TASK_DIR" "<scope>"
uv run ./.trellis/scripts/task.py validate "$TASK_DIR"

If validation fails, fix context paths and re-run validation.

Step 6: Output Summary

Print:

• Task directory path
• Context files configured
• Key technical notes
• Recommended next skill: $dispatch

Before exiting, mark planning steps completed in update_plan.

Guardrails

• Execute real commands; do not only provide a prose plan.
• Keep update_plan synchronized with planning decisions and completion.
• Reject early when requirements are not actionable.
• Keep task scope to one coherent feature.
• Do not invoke legacy multi_agent/*.py scripts for Codex planning.
• Do not commit code in this phase.