generate-session-plans

Convert audit findings into executable remediation sessions by reading docs/audit/REMEDIATION-PLAN.md and individual finding files to produce 2-4 hour work sessions. These sessions feature explicit dependencies and testable acceptance criteria for systematic execution.

Ordering remediation tasks requires building a dependency graph from audit findings to sequence work logically. This approach groups related fixes together, reducing merge conflicts while tying each work item to verifiable regression checks.

Dependency-ordered session planning works by analyzing audit outputs and grouping related fixes into 2-4 hour increments. It establishes explicit prerequisites for each session and enforces automated verification through testable acceptance criteria.

Yes, you can generate qa-session files and a progress tracker from a REMEDIATION-PLAN.md file. The process produces .claude/commands qa-session files, updates orchestration commands, and provides a progress tracker to integrate remediation work.

Yes, individual finding files are needed alongside the REMEDIATION-PLAN.md to create dependency-ordered work sessions. The Skill reads these finding files to build a dependency graph and establish the explicit prerequisites for each session.

Avoid automated session planning for backlog triage when your remediation workflow lacks a structured REMEDIATION-PLAN.md or individual finding files. The process requires these inputs to build dependency graphs and generate sessions with testable acceptance criteria.