paradigm-shift
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.zipInstalls 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.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
When to use paradigm-shift
- →Graduating from phase 0
- →Shifting project focus
- →Closing development sprints
About this skill
Close the current Phase and open the next. This is a deliberate boundary, not a routine increment — and it is user-invoked only: never start it autonomously; go-next suggests it, the user runs it. Challenge whether it's earned before running it.
- Earn it. Confirm the direction has genuinely shifted, or — the first time — that Phase 0's gate is met:
docs/mission.mdis formalized with evidence. If the case is thin, say so and stop. - Record what closed. Summarize what the Phase produced and update
docs/so it reads as the present truth. - Set the next goal. Decide what the next Phase pursues and write it down (e.g. in
docs/roadmap.md). - Reorganize. Adopt any structure the project has now earned (e.g. milestones, a Project).
- Run the git ceremony — on the user's explicit go, and in this order. Archive before you squash: capture the Phase's commit-message journey — how the work unfolded, not the diffs git already keeps — into
archive/and commit it. Then commit the reorg and squash the Phase's commits into one onmain. The squash is a one-way door; the archive is what survives it. Then open the next Phase.
If the shift changes how you work, not just what you're working on, that is a constitutional amendment — open a pull request against CLAUDE.md as part of the reorg.
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.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| paradigm-shift (this skill) | 0 | 1mo | No flags | Advanced |
| task-master | 22 | 5mo | Review | Intermediate |
| github-project-management | 4 | 5mo | Review | Advanced |
| issue-manage | 2 | 4mo | Review | Beginner |
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.
github-project-management
ruvnet
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
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".
issue-maker
pollinations
Create GitHub issues following Pollinations team conventions. Use when asked to create issues, track work, or plan features.
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.
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".