direction-adjust

Record mid-task course corrections as numbered decisions in DECISIONS.md and update TASK_STATE.md.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/Mozurok/fhorja.dev --skill direction-adjust-mozurok
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: direction-adjust
Source: https://github.com/Mozurok/fhorja.dev/tree/main/.claude/skills/direction-adjust
Command: npx skills add https://github.com/Mozurok/fhorja.dev --skill direction-adjust-mozurok

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mid-task realizations about direction changes often go unrecorded, so later sessions lose the reasoning behind a course correction. This Skill captures a small-to-medium adjustment as an auditable, numbered decision entry and keeps task state consistent with the new direction. ## Core Features & Use Cases - Decision Recording: Appends a numbered D-N: mid-task adjustment entry to DECISIONS.md with concise reasoning, and updates TASK_STATE.md fields affected by the change. - Conflict Validation: Checks the adjustment against locked decisions and invariants, routing to decision-interview when a conflict exists instead of silently overwriting. - Smart Routing: Recommends the right next command based on adjustment size, from resuming the current slice to re-planning with implementation-plan or state-reconcile. - Use Case: Halfway through implementing a slice, you realize the data source should be owned by a different module. Use this Skill to record the adjustment, update task state, and get routed back to the correct continuation command. ## Quick Start Ask the assistant to record a mid-task direction adjustment describing what you were doing, what you noticed, and what should change.

Frequently Asked Questions about direction-adjust

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record a mid-task direction change in a task workflow?▼

Describe what you were doing, what you noticed, and what should change. The Skill appends a numbered D-N entry to DECISIONS.md, updates only the affected TASK_STATE.md fields, and recommends the next command based on the adjustment size.

When should I use direction-adjust instead of decision-interview?▼

Use direction-adjust for small-to-medium corrections from your own realization that keep the current slice recoverable. Use decision-interview when the adjustment contradicts a locked decision or requires reopening settled decisions.

What happens if the adjustment conflicts with a locked decision?▼

The Skill validates every adjustment against locked decisions and invariants before writing. On conflict it surfaces the issue explicitly and routes to decision-interview rather than silently overwriting the locked decision.

When should I not use direction-adjust?▼

Avoid it when the trigger is external review feedback, when the realization invalidates the entire task scope, when the change is too small to record, or when no active task folder exists yet.

Does direction-adjust modify the implementation plan?▼

By default it leaves IMPLEMENTATION_PLAN.md unchanged and records the adjustment only in DECISIONS.md. It edits the plan or slice files only when the adjustment changes plan text or slice scope, and routes to re-planning commands when needed.