release-plan

To translate an SRS into GitHub milestones and issues, the Skill reads versioned SRS files via .paadhai.json, analyzes FR-* requirements, groups them into balanced milestones, and generates atomic issues using gh APIs.

Automating release planning from approved requirements to a GitHub project board involves grouping FR-* entries into shippable deliveries, drafting atomic issues with acceptance criteria, and invoking gh APIs to create milestones, issues, and update project board statuses.

Yes, you need a confirmed SRS before generating GitHub milestones. The workflow targets release planning by mapping approved requirements to milestones and issues, requiring SRS files located through .paadhai.json to define shippable deliveries for each development version.

Yes, you can group SRS functional requirements into balanced, shippable GitHub deliveries automatically. The Skill analyzes FR-* entries from the SRS and organizes them into milestones with explicit dependencies for each release version.

Issue generation from an SRS works by drafting atomic issues with clear summaries, acceptance criteria, test checklists, and labels, then assigning them to milestones and adding them to the GitHub project board via gh APIs while tracking progress through an eight-step checklist.

The SRS format for automatic GitHub issue creation requires docs/srs or versioned docs/srs-vX files located by reading .paadhai.json, containing FR-* requirement entries that can be analyzed and mapped to milestones and atomic issues.