feature-estimate-plan

To estimate feature effort across multiple GitHub repositories, this Skill uses the GitHub API for repository exploration and generates a per-repo T-shirt size estimate (XS-XL) alongside an execution plan for scope prioritization.

Evidence-based effort assessment for feature refinement analyzes repository data to provide per-repo estimates, cross-repo effort comparison, and risk analysis, prioritizing evidence-first estimations over guesswork for feasibility assessment.

Yes, you can use Jira context to improve cross-repo effort comparison, as the Skill optionally integrates with Jira for enriched context during the read-only planning mode to generate execution plans.

You map dependencies and identify parallelization opportunities for a new feature by generating an execution plan that identifies the critical path, highlighting risks and unknowns that could impact the implementation timeline.

No, the repository analysis does not alter your codebase during project management planning, as the Skill adheres strictly to a read-only planning mode to assess effort and generate execution plans.

The best way to prioritize scope for a feature spanning multiple repositories is to use per-repo effort estimates and dependency mapping to assess feasibility, compare cross-repo effort, and highlight implementation risks.