What happens if I stop the workflow mid-way?

You can resume by running individual sub-skills like /ctx:architecture or /ctx:techstack. If you re-run /ctx:start, it will detect existing files and enter update mode.

Where does the skill save my project information?

Contextual documentation is stored in the .context/ directory, while your technology stack selections are saved to .project-init.md.

Can I use the start skill on an existing project?

No, this skill is specifically designed for new projects. For existing codebases, you should use the /ctx:onboard skill instead.

Do I have to complete every step in the wizard?

While the wizard is sequential, steps like domain modeling and task breakdown are optional. You can also stop at any point and create epics or tasks later.

Project Startup Wizard

Name: Project Startup Wizard
Author: tdp1999

bytdp1999

0•

Productivity & Workflow

Bootstraps new software projects through a guided workflow including vision, architecture, tech stack, and task planning.

The Project Startup Wizard serves as a master orchestrator for Claude Code, guiding developers through the critical foundational stages of a new project. It automates the creation of essential documentation, from defining the high-level vision and architectural patterns to selecting a technology stack and breaking down the first major feature into actionable tasks. By standardizing the initialization process, it ensures that Claude has all the necessary context to assist effectively from the very first line of code.

Key Features

01Automatic generation of vision, architecture, and tech stack documentation

020 GitHub stars

03Automated directory structure and context initialization

04Interactive epic planning and granular task breakdown

05Optional domain modeling to capture business logic and rules

06Guided end-to-end project initialization workflow

Use Cases

01Bootstrapping a CLI tool or library with standardized documentation

02Planning complex features by breaking them into manageable development steps

03Starting a new SaaS application with a clear architectural roadmap

Key Features

01Automatic generation of vision, architecture, and tech stack documentation

020 GitHub stars

03Automated directory structure and context initialization

04Interactive epic planning and granular task breakdown

05Optional domain modeling to capture business logic and rules

06Guided end-to-end project initialization workflow

Use Cases

01Bootstrapping a CLI tool or library with standardized documentation

02Planning complex features by breaking them into manageable development steps

03Starting a new SaaS application with a clear architectural roadmap