linear-deep-dive

Orchestrating Linear work involves fetching issue or project data, classifying context, exploring relevant code, and coordinating downstream skills for execution. The skill preserves origin details and packages a support kit for review before handoff.

The best way to analyze Linear issues is to fetch the issue data, classify the work scope, and explore relevant code to orchestrate downstream skills. This process preserves provenance and creates an execution plan with a packaged support kit for auditable reviews.

Yes, you can handle both individual Linear issues and full projects. The skill determines the scope by classifying the work and selecting the right workflow, ensuring it respects milestones and dependencies for both issue details and broader project structures.

To preserve provenance when planning work for a Linear issue, the skill maintains origin preservation throughout the fetching, classifying, and execution phases. It provides a public operator packet including a playbook, rubric, and source manifest for auditable handoffs.

Yes, the Linear planning workflow respects project milestones and dependencies. When fetching and analyzing project data, the classification process explicitly accounts for these constraints to guide operators through accurate plan creation and downstream execution.

The operator packet provided before handoff includes a playbook, rubric, and source manifest. This packaged support kit ensures provenance is preserved and enables auditable reviews of the Linear issue or project execution plan.