strategic-to-tactical-workflow

Generate a development plan from a strategic question by running an 8-phase workflow that produces code-grounded specifications, parallel-track decomposition, and automated implementation prompts for the full development cycle.

Orchestrating product planning cycles is best handled by applying strategic scouting and code-base grounding to decompose work into parallel-track specifications, ensuring consistent delivery of planning documents and implementation prompts.

Code grounding within workflow orchestration works by anchoring strategic scouting and specification generation directly to your existing code-base, ensuring parallel-track decomposition aligns with actual development artifacts.

No specific external dependencies are required to run the strategic-to-tactical workflow, as it operates independently using file system and meta-skill dependencies to orchestrate the end-to-end product planning cycle.

You need to generate end-to-end development artifacts for a release when launching a new product cycle, ensuring you have consistent specifications, parallel-track decomposition, and reflections to eliminate ad-hoc planning.

Yes, you can extract meta-skills and learnings after a development cycle because the workflow includes a post-cycle reflection phase designed to capture insights for future strategic-to-tactical planning.