project-plan

The skill transforms ambiguous product ideas into a confirmed SRS document by orchestrating a 10-step workflow that clarifies context, researches constraints, creates templated sections, and presents them for stakeholder approval before saving.

Deriving the correct SRS path involves config-aware context loading where the skill reads the `.paadhai.json` file, extracts the project_version, and loads prior SRS files from the docs folder to maintain versioned context before planning new features.

You create structured requirements for a release by triggering the guided planning workflow, which executes steps from initial clarifying questions through research and templated section generation to produce a vetted SRS document for stakeaker approval.

Yes, you need an existing `.paadhai.json` file and a docs folder in a Paadhai-managed repository, as the skill applies config-aware context loading to read configuration and derive the correct versioned SRS path before generating documentation.

Confirmed SRS documents are delivered by saving the generated files into the docs folder and committing them to the repository with standardized messaging, ensuring consistent version control and immediate handoff for release-facing actions.