A controlled process for closing one development phase and opening the next.

Install

mkdir -p .claude/skills/paradigm-shift && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/19101" && unzip -o skill.zip -d .claude/skills/paradigm-shift && rm skill.zip

Installs to .claude/skills/paradigm-shift

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Close one development Phase and open the next when the project's direction shifts — or, the first time, to graduate out of Phase 0. Squashes the chapter into one commit, archives the history, ratifies the organization the phase produced, and sets the next Phase's goal. Triggers on "paradigm shift", "close this phase", or graduating from Phase 0.
347 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Advanced

Key capabilities

  • →Summarize what a development phase produced
  • →Update documentation to reflect current truth
  • →Define the goal for the next development phase
  • →Reorganize project structure based on earned changes
  • →Archive commit history before squashing

How it works

This skill closes a development phase by summarizing its output, updating documentation, defining the next phase's goal, and reorganizing the project. It performs a git ceremony to archive the commit history before squashing the phase's commits into one.

Inputs & outputs

You give it
Current development phase, project documentation, commit history
You get back
Updated documentation, defined next phase goal, archived history, squashed commits

When to use paradigm-shift

  • →Graduating from phase 0
  • →Shifting project focus
  • →Closing development sprints

About paradigm-shift

Squashes phase commits, archives project history, updates organizational documentation, and sets goals for the upcoming development period.

Close one development Phase and open the next when the project's direction shifts — or, the first time, to graduate out of Phase 0. Squashes the chapter into one commit, archives the history, ratifies the organization the phase produced, and sets the next Phase's goal. Triggers on "paradigm shift",

When not to use it

  • →When a routine increment is needed
  • →When the user has not explicitly invoked the skill
  • →When the direction has not genuinely shifted

Limitations

  • →User-invoked only, never autonomous
  • →Requires confirmation of a genuine direction shift
  • →Squashing commits is a one-way door

How it compares

This skill formalizes the transition between significant development phases with explicit documentation updates and a git ceremony, unlike informal phase changes or simple commit squashing.

Compared to similar skills

paradigm-shift side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
paradigm-shift (this skill)04moNo flagsAdvanced
task-master228moReviewIntermediate
github-project-management48moReviewAdvanced
issue-manage27moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

task-master

sfc-gh-dflippo

AI-powered task management for structured, specification-driven development. Use this skill when you need to manage complex projects with PRDs, break down tasks into subtasks, track dependencies, and maintain organized development workflows across features and branches.

22131

github-project-management

ruvnet

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

427

issue-manage

catlog22

Interactive issue management with menu-driven CRUD operations. Use when managing issues, viewing issue status, editing issue fields, performing bulk operations, or viewing issue history. Triggers on "manage issue", "list issues", "edit issue", "delete issue", "bulk update", "issue dashboard", "issue history", "completed issues".

24

issue-maker

pollinations

Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.

14

create-issue

dotCMS

Create GitHub issues using repository templates. Use when the user asks to create an issue, bug report, feature request, task, spike, epic, or UX requirement. Also use when the user describes a problem, bug, enhancement, or work item that should be tracked. Supports both English and Spanish input.

13

issue-discover

catlog22

Unified issue discovery and creation. Create issues from GitHub/text, discover issues via multi-perspective analysis, or prompt-driven iterative exploration. Triggers on "issue:new", "issue:discover", "issue:discover-by-prompt", "create issue", "discover issues", "find issues".

11

Search skills

Search the agent skills registry