start

Routes new project conversations to the correct starting phase based on opening message signals.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/scoots31/engineering-playbook --skill start-scoots31
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start
Source: https://github.com/scoots31/engineering-playbook/tree/main/skills/start
Command: npx skills add https://github.com/scoots31/engineering-playbook --skill start-scoots31

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a solo builder opens a new conversation with an AI assistant, they should not have to know which phase of a software-building framework applies to their idea. This Skill reads the opening message, checks for existing project context, and silently routes the conversation to the right starting point — Brainstorm, Discover, onboarding, or a resumed session — without exposing any framework mechanics to the user. ## Core Features & Use Cases - Automatic context detection: Scans for existing artifacts like BLUEPRINT.md, discovery briefs, design docs, and handoff files before deciding whether to route or simply continue existing work. - Three-shape classification: Classifies opening messages as clear ideas (route to Discover), exploratory thinking (route to Brainstorm), or ambiguous (ask one resolving question). - Named project resume: Recognizes "guided on [name]" or "resume [name]" prompts, looks up the project registry, and orients from the handoff file in one sentence. - Deployed project new-cycle handling: When a shipped project gets new work, opens a new phase record in the backlog and routes to the appropriate skill without touching completed phases. - Use Case: A user opens Cursor and types "I want to build a tool that tracks my freelance invoices." The Skill detects no existing context, classifies this as a clear idea, and begins discovery questions immediately — the user never sees any routing happen. ## Quick Start Start a new conversation describing your project idea and let the assistant determine whether to brainstorm, discover, or resume existing work.

Frequently Asked Questions about start

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

FAQPage Schema
How do I start a new project with an AI coding assistant framework?

Simply describe your idea in the opening message. The start skill checks for existing project context, classifies your idea as clear or exploratory, and routes you to discovery or brainstorming automatically without announcing any phases.

How does conversation routing decide between brainstorm and discovery?

Routing classifies the opening message into three shapes: clear ideas with defined who/what/value go to Discover, exploratory thinking-out-loud goes to Brainstorm, and ambiguous openings get one clarifying question before routing.

Can I resume a named project in a new session?

Yes. Say "guided on [name]", "resume [name]", or "pick up [name]" and the skill looks up the project in the projects registry, reads the handoff file's current-state sections, and orients you in one sentence.

What happens when I add new work to an already deployed project?

The skill treats it as a new cycle, not a resume. It opens a new phase record in the backlog, updates the handoff file, and routes to discovery, design review, enhancement, or bug fix depending on the scope of the new work.

When does the start skill not fire?

It does not fire when existing project context is found, when a build is mid-progress, when a discovery brief or blueprint already exists, or when another skill is already active. In those cases it orients to current state and continues.