start

Automate new project initialization with vision, architecture, techstack, and epic planning.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/tdp1999/claude-code-ctx --skill start-tdp1999
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/tdp1999/claude-code-ctx/tree/main/plugins/ctx/skills/start
Command: npx skills add https://github.com/tdp1999/claude-code-ctx --skill start-tdp1999

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the setup of a new project by guiding users through the complete initialization workflow, reducing setup time and ensuring consistency across projects.

Core Features & Use Cases

  • End-to-end onboarding: Guides vision, architecture, techstack, and initial planning for a fresh project.
  • Incremental outputs: Creates structured artifacts like vision, architecture, techstack, domain (optional), epics, and task plans as the project progresses.
  • Resumable flow: Allows independent re-use of sub-skills (e.g., /ctx:vision, /ctx:architecture) to update or continue the workflow.

Quick Start

Start by providing an optional project idea; the skill will guide you through vision, architecture, and tech choices.

Frequently Asked Questions about start

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

FAQPage Schema
How do I automate project initialization for a new software architecture?

You can automate project initialization by orchestrating end-to-end workflows that define your vision, architecture, techstack, and epic planning. This generates structured artifacts like .context/vision.md and .project-init.md for new projects.

Can I resume project planning if I stop halfway through the workflow?

Yes, the project planning workflow supports resumable progress. You can independently re-execute specific sub-skills like /ctx:vision or /ctx:architecture to update or continue generating your project artifacts at any time.

What structured outputs are generated during project setup?

Project setup generates structured artifacts including .context/vision.md, patterns-architecture.md, .project-init.md, and optional domain and epic artifacts. These files ensure consistency and provide a clear reference for your techstack and task plans.

Does this workflow support adding domain-specific planning to an existing project?

No, this workflow applies to new projects only. However, you can use the independent /ctx:domain sub-skill to generate optional domain artifacts that integrate into your broader architecture and epic planning during initialization.

What is the best way to break down epics after defining a techstack?

After defining your techstack, use the /ctx:breakdown sub-skill to generate structured epic and task plans. This incremental process creates detailed artifacts that guide development based on your established architecture and vision.