What problem does it solve?
Monorepos and multi-application repositories often produce a flat stream of chat requests that hide ownership, priority, and scope; this Skill organizes incoming work into portfolio, app, feature, and task layers so teams can plan, approve, and execute with clear visibility.
Core Features & Use Cases
- Classification: Decide whether a request belongs to portfolio, app/area, feature, or task scope and separate mixed-level requests before implementation.
- Area selection and focus: Use the monorepo map to pick a target area, explicitly name additional affected areas, and apply area-focused workflows such as /focus.
- Planning gate and visible tasks: Gate feature-sized work with a planning step (/plan), save and seek approval, then create labeled Beads epics and tasks to preserve human visibility and traceability.
- Use Case: For a cross-app feature, list affected areas, run a plan and checkpoint approval, then create Beads epics and child tasks with consistent labels so stakeholders can triage and prioritize.
Quick Start
Classify the request as portfolio, app, feature, or task, select the target area, run planning for feature-sized work, and create visible Beads tasks for implementation and approval.
