major-task

Analyze repository evidence to propose architecture, migration, or benchmark decisions.

434|33|Updated Jul 27, 2025
One-click install
npx skills add https://github.com/udecode/kitcn --skill major-task
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: major-task
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/major-task
Command: npx skills add https://github.com/udecode/kitcn --skill major-task

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Take on heavyweight architectural, comparative, benchmark, migration, or proposal-grade work where wrong framing is costly, delivering deep, explicit analysis and a clear handoff.

Core Features & Use Cases

  • Architecture or public API redesigns, cross-package refactors, RFC-like proposals, and major migration planning.
  • Repo-grounded planning: uses repository evidence to guide decisions, avoiding external takes and scope creep.
  • Structured handoff: delivers a phased plan, criteria, and artifacts ready for review.

Quick Start

Provide a planning-first analysis for an architectural decision within the repository.

Frequently Asked Questions about major-task

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

FAQPage Schema
How do I plan an architecture redesign using repository evidence?

To plan an architecture redesign using repository evidence, this Skill analyzes your codebase to propose grounded decisions, delivering a structured plan with explicit criteria, phased rollout, and a concise handoff ready for review.

What is the best way to write an RFC-style proposal for a major codebase migration?

For an RFC-style proposal for a major codebase migration, this Skill generates a structured decision plan grounded in repository evidence, covering scope, phased rollout steps, and artifacts ready for team review.

Can I use this for cross-package refactors and benchmark decisions?

Yes, you can use this Skill for cross-package refactors and benchmark decisions. It scopes major changes within the codebase and outputs a structured decision plan with explicit criteria and a concise handoff.

How does repo-grounded research prevent scope creep during major changes?

Repo-grounded research prevents scope creep by using repository evidence to guide decisions, avoiding external assumptions and ensuring the architectural analysis stays strictly framed within your codebase's actual structure.

Do I need to provide a specific architectural decision to get a phased rollout plan?

You need to provide a planning-first analysis target for an architectural decision within the repository. The Skill then processes this to output a structured handoff with explicit criteria and a phased rollout plan.