transition

Verify task summaries and update project documentation to advance phases.

Updated Jan 12, 2026
One-click install
npx skills add https://github.com/sidunrealde/ArchVis --skill transition-sidunrealde
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: transition
Source: https://github.com/sidunrealde/ArchVis/tree/main/.github/skills/transition
Command: npx skills add https://github.com/sidunrealde/ArchVis --skill transition-sidunrealde

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gsd-tools, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of marking a project phase as complete, updating project documentation, and preparing for the next phase, ensuring smooth project progression and accurate progress tracking.

Core Features & Use Cases

  • Phase Completion Verification: Checks if all planned tasks for the current phase are summarized.
  • Automated Documentation Updates: Updates PROJECT.md, ROADMAP.md, and STATE.md to reflect phase completion and next steps.
  • Progress Tracking: Ensures project status and roadmap accurately reflect completed work.
  • Use Case: After completing the development of a feature in Phase 2, you use this Skill to mark Phase 2 as done, update the project roadmap, and automatically set up the state for planning Phase 3.

Quick Start

Use the transition skill to mark the current phase as complete and advance to the next.

Frequently Asked Questions about transition

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

FAQPage Schema
How do I automate project phase transition and update documentation?

Automating project phase transition involves verifying task summaries and automatically updating ROADMAP.md and PROJECT.md. This process verifies completion, updates project state files, and advances the project to the next phase.

What is the best way to update ROADMAP.md and PROJECT.md after a project phase?

Updating ROADMAP.md and PROJECT.md after a phase requires verifying all planned tasks are summarized. The transition process automatically updates these files to reflect completion and sets up the state for planning the next phase.

Do I need gsd-tools CLI to manage workflow automation for phase transitions?

Yes, the gsd-tools CLI is required to manage workflow automation for phase transitions. It provides the comprehensive state and roadmap management capabilities required to verify and advance the project state.

How does progress tracking work when completing a project phase?

Progress tracking during phase completion works by checking if all planned tasks are summarized. It then updates the project status and roadmap to accurately reflect completed work before advancing to the subsequent phase.

Can I mark a phase as complete if planned tasks are not summarized?

No, you cannot mark a phase as complete without summarizing planned tasks. The phase completion verification step explicitly checks that all planned tasks for the current phase are summarized before allowing the transition.