akrctx-workflowlisted

# akrctx-workflow Use the workflow named in the task capsule. ## fast-patch 1. Load only the files directly touched by the change. 2. Make the smallest safe edit that satisfies the goal. 3. Verify the change does not break adjacent behavior. 4. No spec or new tests unless they already exist. ## research-first 1. Read .akrctx/config.json, policy.json, and relevant wiki pages without modifying code. 2. Inspect relevant files, git log, and .akrctx/wiki/decisions.md. 3. List open questions and areas of uncertainty in the task capsule. 4. Propose an approach and wait for user confirmation before implementing. 5. Switch to a concrete workflow (TDD, SDD, etc.) for implementation. ## SDD 1. Write or update the behavior contract: inputs, outputs, preconditions, postconditions, and explicit out-of-scope boundaries. 2. Record the contract in the task capsule before touching implementation files. 3. Implement only what the contract specifies. ## TDD 1. Write failing tests that encode the expected behavior. Confirm they fail for the right reason. 2. Implement the minimum code to make the tests pass. 3. Refactor if needed, keeping tests green. ## EDD 1. Define concrete examples and edge cases: happy paths, empty inputs, boundary values, unexpected combinations. 2. Record examples in the task capsule. 3. Implement against those examples. ## SDD+TDD 1. Write the behavior contract (SDD). 2. Encode the contract as failing tests (TDD). 3. Implement until tests pass. ## SDD+EDD 1.