major-task

Coordinate complex architectural tasks through a structured research-first workflow.

Updated Jul 18, 2026
One-click install
npx skills add https://github.com/arthrod/conejo-skills --skill major-task-arthrod
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: major-task
Source: https://github.com/arthrod/conejo-skills/tree/main/skills/major-task
Command: npx skills add https://github.com/arthrod/conejo-skills --skill major-task-arthrod

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of high-stakes, complex decision-making in software projects by enforcing a rigorous, research-first methodology that prevents costly architectural errors and bloated implementations.

Core Features & Use Cases

  • Architectural Research: Systematically maps seams, ownership, and public API boundaries before proposing changes.
  • Evidence-Based Planning: Integrates repository-wide pattern recognition and performance benchmarking to ground decisions in facts rather than assumptions.
  • Use Case: Use this when you need to perform a major cross-package refactor, compare editor frameworks, or design a new public API that requires deep repo-grounding and stakeholder alignment.

Quick Start

Use the major-task skill to analyze the proposed migration of our core editor framework and provide a feasibility report based on existing repository patterns.

Frequently Asked Questions about major-task

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a major framework migration without breaking existing architecture?

A public API redesign requires systematic mapping of ownership boundaries and existing repository patterns before implementation. Evidence-based planning integrates performance benchmarking and pattern recognition to ground architectural decisions in repository facts, ensuring stakeholder alignment and maintainability.

What is the best way to structure an RFC for a cross-package refactoring project?

An RFC-grade proposal for cross-package refactoring should define explicit decision criteria and document repository-wide pattern recognition. Structured research-first methodology prevents costly architectural errors by enforcing rigorous analysis of seams, ownership, and API boundaries before phased implementation begins.

Can I use this research-first workflow for comparative analysis of different architectural patterns?

Comparative analysis of architectural patterns fits this workflow when high-stakes engineering decisions are involved. The structured methodology requires deep repository grounding and explicit decision-criteria definition to evaluate options systematically, ensuring technical coherence in framework comparisons and performance benchmarking tasks.

When do I need performance benchmarking for architectural decision-making?

This structured workflow suits high-stakes architectural tasks like framework migrations, cross-package refactors, and public API redesigns that require stakeholder alignment. If your task lacks deep repository grounding needs or explicit decision-criteria definition, a lighter planning approach may be more appropriate.