feature-planning

To create an implementation-ready plan for a feature in a monorepo, define the feature scope and repository constraints to generate a numbered overview, per-module implementation files, and a testing plan saved under plans/{feature_name}/.

Preventing context rot during feature handoff requires converting a bounded feature request into a durable, implementation-ready plan with clear implementation order and a required testing checklist for engineers to follow without extra context overhead.

Structuring a testing plan for multi-language monorepo features involves creating a required testing checklist saved alongside a numbered overview and per-module implementation files within the plans/{feature_name}/ directory for immediate validation.

Yes, this feature planning approach works with live and research repository boundaries by inferring repository constraints across apps/web, services/*, apps/research, and libs/* to keep live versus research boundaries intact during scoped feature planning.

You need to refine an epic child into a separate implementation plan when you have a single bounded feature within a multi-language monorepo that requires clear implementation order and testing handoff to prevent context rot.

To generate per-module implementation files for scoped features, confirm the feature name, scope, and target repo area, then read relevant initiative or epic docs to produce implementation-ready artifacts written directly to the plans/{feature_name}/ directory.