autospec.implement

User Input

$ARGUMENTS

You MUST consider the user input before proceeding (if not empty).

Execution Boundaries (CRITICAL)

Flag	Behavior
--phase N	Execute ONLY phase N tasks. After completion, output "Phase N complete." and TERMINATE. Do NOT proceed to other phases.
--context-file	Use bundled artifacts from context file. Do NOT separately read files listed in _context_meta.skip_reads.
(no flags)	Execute all phases sequentially.

Pre-computed Context

The following paths have been pre-computed and are available for use:

• FEATURE_DIR: {{.FeatureDir}}
• TASKS_FILE: {{.TasksFile}}
• CONSTITUTION_FILE: {{if .ConstitutionFile}}{{.ConstitutionFile}}{{else}}not found{{end}}
• IS_GIT_REPO: {{.IsGitRepo}}

Outline

1. Phase Context Metadata (CRITICAL - Token Optimization):

   Check if --context-file was used. If so, parse the _context_meta section FIRST before any other file reads.

   _context_meta Fields:

   • phase_artifacts_bundled: true - Indicates that spec.yaml, plan.yaml, and tasks.yaml (phase-filtered) are already bundled in this context file
   • bundled_artifacts - Lists the artifacts included, such as ["spec.yaml", "plan.yaml", "tasks.yaml (phase-filtered)", "constitution.yaml"]
   • has_governance - Boolean indicating whether project governance is bundled in the governance: section
     • If true: Use the bundled governance: data as the constitution/governance source of truth
     • If false: No constitution was bundled; do not search for a governance file during context-file execution
   • governance_file - Path to the constitution file when governance is bundled
   • has_checklists - Boolean indicating whether a checklists/ directory exists for this feature
     • If false: DO NOT check for, scan, or read from the checklists directory - it doesn't exist, skip step 3 entirely
     • If true: Checklists directory exists, proceed to step 3
   • skip_reads - Explicit list of file paths that are already bundled and MUST NOT be read separately