preset-trigger · git:20260707.8005b52 · 2026-07-07 · sha256 9a9b629c80b70b75
preset-trigger git:20260707.8005b52A
Immutable. This exact content is served forever at /api/v1/blob/9a9b629c80b70b75.
--- name: preset-trigger description: Start Harness Anything task creation by choosing a software/coding preset first. Use when creating or planning a harness task package. --- # Preset Trigger ## Core Rule When building a Harness Anything task, choose the preset before creating the task package. Presets are the recommended starting points for task shape, checks, and generated materials. Use: ```bash ha task create --title "<title>" --vertical software/coding --preset <id> ``` If unsure, inspect the current list first: ```bash ha task create --help ha preset list ha capabilities preset ``` ## Available Presets - `standard-task`: General implementation or maintenance task; the default starting point. - `decision-conformance`: Work that must prove alignment with recorded decisions. - `milestone-closeout`: Milestone wrap-up checks and evidence collection. - `module`: Module-scoped task with registered module metadata. - `subtask-expansion`: Plan and fan out a parent task into concrete subtasks. - `long-running-task`: Extended task that needs explicit long-running coordination. - `legacy-migration`: Legacy task intake or migration planning. - `dogfood-utilization-audit`: Audit whether Harness presets and artifacts are being used. - `doc-canon-sync`: Documentation canon synchronization work. - `lesson-sedimentation`: Promote useful lessons from task evidence. - `gate-architecture-retrospective`: Review gate architecture and enforcement posture. - `milestone-dossier`: Generate a milestone dossier from project evidence. - `version-upgrade`: Version upgrade planning and execution support. - `publish-standard`: Publish readiness and capability smoke workflow. - `release-closeout`: Release wrap-up and evidence checks. ## Guardrails - Do not hand-create task package directories. - Do not skip preset selection for software/coding work; use `standard-task` when no narrower preset fits. - Do not edit task markdown directly when a `ha task create` path is available.