trio:subsprint-planner

The planner converts inputs from three sources into a standardized plan file. It validates preconditions, enforces front-matter and checklist contracts, then routes to bugfix-plan, urs-gap-plan, or subsprint-fresh-plan sources.

After subsprint plan generation, the recommended sequence is to run the subsprint runner followed by the subsprint sync. This sequence ensures the generated plan is executed and synchronized properly within the workflow.

Subsprint planning dispatches inputs to bugfix-plan, urs-gap-plan, or subsprint-fresh-plan sources based on input type. Each source generates a plan file while maintaining a consistent folder layout under the subsprint directory.

Yes, the planner validates preconditions automatically before generating a subsprint plan file. It enforces the Plan Front-Matter Contract and the Plan Checklist Contract to ensure the generated plan meets required structural standards.

The subsprint planner enforces a consistent folder layout under trio/subsprint. Plan files are drafted as markdown files within a numbered, date-stamped, and word-tagged subdirectory for organized tracking.

Yes, you can use the planner for workflow automation by selecting the subsprint-fresh-plan source. This allows you to generate a plan file without relying solely on a product requirements document.