plan-start-core

Generate a planning workspace with intake, PRD, manifest.json, and state.json files.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/KGmufassa/Escrolly --skill plan-start-core
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: plan-start-core
Source: https://github.com/KGmufassa/Escrolly/tree/main/.opencode/skills/plan-start-core
Command: npx skills add https://github.com/KGmufassa/Escrolly --skill plan-start-core

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Drafts an initial planning setup by translating a new app idea into a ready-to-use planning workspace, intake, PRD, manifest.json, and state.json using repository templates as the source of truth.

Core Features & Use Cases

  • Automated workspace initialization using Planning Template references to produce PRD, intake, and configuration artifacts.
  • Generates manifest.json and state.json to provide deterministic scaffolding for a single app idea.
  • Supports both command-driven execution and an interactive fallback for planning on demand.

Quick Start

Run plan-start-core to bootstrap the planning workspace for a new app idea.

Frequently Asked Questions about plan-start-core

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

FAQPage Schema
How do I auto-initialize a planning workspace for a new app idea?

To auto-initialize a planning workspace for a new app idea, run the command to draft an initial planning setup that generates intake, PRD, and configuration artifacts automatically.

What files are generated when bootstrapping a PRD and intake scaffold?

Bootstrapping a PRD and intake scaffold generates App-Idea-Intake documents, PRD artifacts, and deterministic manifest.json and state.json files for state tracking.

Can I use interactive mode for planning workspace initialization?

Yes, you can use interactive mode for planning workspace initialization as a fallback, allowing you to plan on demand when command-driven execution is not suitable.

Do I need existing repository templates to generate a PRD and intake artifacts?

Yes, you need existing repository templates because the workspace initialization uses Planning Template references as the source of truth to generate the PRD and intake artifacts.

What is the best way to set up deterministic state tracking for a new product idea?

The best way to set up deterministic state tracking for a new product idea is by generating a manifest.json and state.json alongside the PRD to provide a ready-to-use planning scaffold.

Are there limitations when using planning templates to draft an initial planning setup?

A limitation of using planning templates to draft an initial planning setup is that outputs are deterministic and designed for a single app idea, requiring separate runs for multiple projects.