plan-issue

To create an implementation plan for a GitHub issue in a monorepo, you can automate context gathering and scope mapping. This process fetches issue details and aligns steps with existing codebase patterns, architectural decisions, and cross-scope dependencies to reduce planning errors.

The best way to map monorepo scope is by identifying affected packages like core, api, agent, or pipeline, and aligning implementation steps with scope-specific guidelines. This ensures your feature request matches existing codebase patterns and catches cross-scope dependencies.

Yes, you need to check architectural decision records before coding a new pipeline to validate relevant context. Automated planning checks existing ADRs to flag if a new record is needed for your ingestion source, ensuring consistent implementations and preventing rework.

Automated issue planning handles sub-issues and comments by fetching all metadata from the repository. This full context gathering captures all requirements and discussions, ensuring your implementation steps account for every functional constraint before development begins.

Yes, you can use scaffold skills to accelerate implementation planning by mapping applicable templates to your issue. This references relevant scaffold skills for tasks like pipeline creation, speeding up development while adhering to established architectural patterns.