plan-sync-ssot

To sync a finalized plan into GitHub Issues, this Skill creates a structured hierarchy featuring a parent issue and 3-6 child issues. It translates the plan into actionable tasks, automatically populating each child issue with the original prompt, scope, acceptance criteria, and base commit SHA.

Structuring GitHub Issues from an AI-assisted planning session is best handled by generating a parent issue for the overall plan and 3-6 child issues for executable tasks. This ensures every child issue contains essential details like scope, acceptance criteria, and base commit information for clear linkage.

Yes, the plan-sync-ssot Skill works without additional dependencies or components listed in its setup. It operates as an automation tool that directly synchronizes your finalized plan into a structured hierarchy of GitHub Issues, reporting the sync status as PASS or BLOCKED.

A GitHub Issue sync reports a BLOCKED status when the finalized plan cannot be properly translated into a structured hierarchy of parent and child issues. The Skill evaluates the proposed plan and actionable tasks, returning BLOCKED if the sync process encounters issues generating the 3-6 child issues.

Yes, you can automate task management by creating a parent issue representing the overall plan alongside 3-6 child issues for individual executable tasks. This automation structures actionable tasks in GitHub Issues, detailing each with the original prompt, scope, acceptance criteria, and base commit SHA.

You need to generate a single source of truth issue tree in GitHub after finalizing a proposed plan from an AI-assisted planning session. This process creates a structured hierarchy of GitHub Issues, ensuring development teams have clearly defined, linked, and actionable tasks to execute.