list-phase-assumptions
Surface Claude's assumptions about a phase approach before planning
Browse published AI skills maintained by XcluEzy7. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
94Repository stars across indexed skills
0Repository forks
0Average repository stars per indexed skill
0Repository stars may repeat across skills from the same repository.
Surface Claude's assumptions about a phase approach before planning
Start a new milestone cycle — update PROJECT.md and route to requirements
Gather context for next milestone through adaptive questioning
Create detailed execution plan for a phase (PLAN.md)
Research domain ecosystem before creating roadmap
Insert urgent work as decimal phase (e.g., 72.1) between existing phases
Check project progress, show context, and route to next action (execute or plan)
Strategies for estimating scope and maintaining quality in autonomous plans
Create roadmap with phases for the project
Archive completed milestone and prepare for next version
Create detailed execution plan for a phase (PLAN.md)
Add phase to end of current milestone in roadmap
Create phases to close all gaps identified by milestone audit
Remove a future phase from roadmap and renumber subsequent phases
Create context handoff when pausing work mid-phase
Research how to implement a phase before planning
Collaborative questioning techniques to extract vision and requirements
Create comprehensive Product Requirements Documents (PRDs)
Comprehensive research for projects and phases, covering domain ecosystems, implementation strategies, and quality improvement to avoid common pitfalls
Derive requirements by working backwards from the goal
Research web applications and competitors using automated browser interactions
Gather phase context through adaptive questioning before planning
Validate built features through conversational UAT
Verification Patterns
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.