align-planning

Generate a Planning Alignment Report with a machine-readable drift block.

7|3|Updated Jan 23, 2026
One-click install
npx skills add https://github.com/nesnilnehc/ai-cortex --skill align-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: align-planning
Source: https://github.com/nesnilnehc/ai-cortex/tree/main/skills/align-planning
Command: npx skills add https://github.com/nesnilnehc/ai-cortex --skill align-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Post-task traceback and drift detection to keep planning elements (goals, requirements, milestones, roadmap) aligned with task execution, reducing misalignment and rework.

Core Features & Use Cases

  • Post-task alignment and drift detection across backlog, roadmap, milestones, and requirements.
  • Top-down recalibration with actionable next steps and prioritized tasks.
  • Evidence-ready reporting with a JSON/YAML drift block.

Quick Start

Run align-planning after a completed task to generate a Planning Alignment Report and drift block.

Frequently Asked Questions about align-planning

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

FAQPage Schema
How do I detect planning drift after a task is completed?

To detect planning drift after a task, perform a post-task traceback to compare execution against backlog, roadmap, and milestone goals, generating a machine-readable drift block and alignment report.

What is post-task traceback for roadmap and milestone alignment?

Post-task traceback is a recalibration mechanism ensuring roadmap and milestone alignment by mapping completed task execution back to original requirements, detecting drift, and outputting actionable next steps.

How do I recalibrate milestones and releases after task execution?

You can recalibrate milestones and releases through top-down recalibration, which uses post-task trace mappings to identify misalignment and generate prioritized tasks to correct planning drift.

Do I need trace mappings to generate a planning alignment report?

Yes, generating a planning alignment report requires a completed task description and trace mappings as inputs to accurately detect drift and output the calibration report in markdown format.

What's the best way to keep requirements aligned with task execution?

The best way to keep requirements aligned is running a post-task traceback to detect execution drift, followed by top-down recalibration outputting actionable next steps and a machine-readable drift block.