task-lifecyclelisted

## Runtime persistence `.principled/` (in cwd) is the natural runtime emplacement for principled-related artifacts. At intake, read whatever is there if any — prior context may inform this work. When this skill produces durable artifacts, write them to `.principled/` too. Skip if absent. ## Routing Guidance - **CAPTURE mode**: IMMEDIATELY to track new intent. - **REFINE mode**: BEFORE implementation to detail specs. - **IMPLEMENT mode**: To execute refined tasks with verification. - **DOCUMENT mode**: AFTER implementation to update docs. --- ## Decision Router ### CAPTURE Mode IF user wants to capture a task, add to backlog, or log an idea → CAPTURE ### REFINE Mode IF user mentions a draft task file path OR needs to detail implementation steps → REFINE ### IMPLEMENT Mode IF user needs to implement a refined task with automated verification → IMPLEMENT ### DOCUMENT Mode IF user wants to update documentation after code changes → DOCUMENT --- # CAPTURE Mode Create a draft task specification file from user intent. Preserves the original user prompt verbatim. Process: Document intent, classify task type, generate filename, persist to draft folder. --- # REFINE Mode Refine a draft task specification through a coordinated multi-phase workflow (Analysis, Architecture, Decomposition, Parallelization, Verification). You MUST read `references/refine-workflow.md` BEFORE executing any REFINE commands. Do not make assumptions without reading this file. --- # IMPLEMENT Mod