start-project

Initialize tracked JellyRock projects with charters and project scaffolding.

37|2|Updated Jun 28, 2025
One-click install
npx skills add https://github.com/jellyrock/jellyrock --skill start-project-jellyrock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: start-project
Source: https://github.com/jellyrock/jellyrock/tree/main/.claude/skills/start-project
Command: npx skills add https://github.com/jellyrock/jellyrock --skill start-project-jellyrock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the risk of disorganized, untracked multi-session work on JellyRock by providing a standardized, repeatable process to start new tracked projects with a clear, collaboratively designed charter, preventing scope drift and lost work across sessions.

Core Features & Use Cases

  • Automated Project Scaffolding: Runs a deterministic, error-checked script to create the project directory, generate a PLAN.md from the official template, fill in dated frontmatter, and index the project in the projects README, eliminating manual setup errors and duplicate work.
  • Interactive Charter Co-Design: Guides collaborative discussion to define the project Goal, Success criteria, Out of scope, and Phases, ensuring full alignment on scope before any work begins.
  • Duplicate Slug Protection: Automatically checks for existing projects with the same slug (including archived projects) to prevent accidental overwrites of prior work and routes users to the correct resume workflow if a duplicate is found. Use Case: For a multi-session effort like implementing a new JellyRock playback feature that spans design, development, and testing across multiple work sessions, use this skill to set up a tracked project with a clear plan and enforced session lifecycle.

Quick Start

Invoke the start-project skill with your desired project slug (for example, "playback-redesign") to scaffold a new tracked JellyRock project and begin co-designing its charter with the guided workflow.

Frequently Asked Questions about start-project

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

FAQPage Schema
How do I start a tracked multi-session project with a formal charter?

To start a tracked multi-session project, invoke the skill with a project slug like "playback-redesign" to scaffold the directory, generate PLAN.md from the official template, and begin co-designing the charter through a guided interactive workflow.

What is project scaffolding for multi-session development work?

Project scaffolding for multi-session work is a standardized process that creates a project directory, fills in dated frontmatter, and indexes the project in a README to prevent scope drift and lost work across sessions.

How does duplicate slug detection work when initializing a new project?

Duplicate slug detection checks for existing projects, including archived ones, with the same identifier during initialization to prevent accidental overwrites, routing users to the correct resume workflow if a collision is found.

Can I use this project initialization process for refactoring and bug fix campaigns?

Yes, you can use this initialization process for any multi-session effort crossing phase boundaries, including feature development, bug fix campaigns, and refactoring initiatives that require recording architectural decisions.

What's the best way to prevent scope drift across multiple work sessions?

The best way to prevent scope drift is to co-design a formal charter defining the project Goal, Success criteria, Out of scope, and Phases collaboratively before any development work begins, ensuring full alignment on scope.

Why does untracked multi-session development work cause problems?

Untracked multi-session development causes problems because work context is lost between sessions, leading to disorganized efforts and scope drift without a standardized process to initialize projects with clear plans.