starting-a-new-project

Automate new project setup runbooks from naming validation to scaffold issue generation.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/michaelkd01/dic-skills --skill starting-a-new-project
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: starting-a-new-project
Source: https://github.com/michaelkd01/dic-skills/tree/main/starting-a-new-project
Command: npx skills add https://github.com/michaelkd01/dic-skills --skill starting-a-new-project

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Projects often start with inconsistent naming, documentation, and scaffolding, so this runbook enforces a deterministic workflow that walks from naming validation through Notion and Paperclip setup to scaffold preparation and clone map updates to prevent missed steps.

Core Features & Use Cases

  • Consistent Naming & Validation: Confirm folder conventions, unique project codes, and derive the repository path before moving forward.
  • Notion & Paperclip Coordination: Create the Paperclip project, update PROJECT DOCS select options, and batch-create Overview, Architecture, Roadmap, and Chat Log pages to keep documentation structured.
  • Scaffold, Clone Map, and Summary Delivery: Queue a scaffold issue with detailed metadata, note the required clone map edits for the nightly audit, and summarize the entire initialization for the user.
  • Use Case: Kick off a new TypeScript/Next.js initiative so the executor immediately receives the scaffold task while the Mac Mini clone map stays synchronized.

Quick Start

Begin by collecting project naming, code, folder, stack, and purpose details, then carry out the phases in order: naming validation, Notion setup, scaffold creation, clone map updates, and summary delivery.

Frequently Asked Questions about starting-a-new-project

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

FAQPage Schema
How do I automate project kickoff for a Next.js or Swift initiative using Notion?

Automate project kickoff by validating naming conventions, creating the Paperclip project, batch-creating Notion Overview and Architecture pages, and queueing scaffold issue metadata for Python, TypeScript/Next.js, or Swift stacks.

What is a project setup runbook and how does it coordinate Notion and repository scaffolding?

A project setup runbook coordinates Notion page batch-creation, Paperclip project setup, repository scaffold issue queuing, and clone map synchronization to prevent missed onboarding steps.

Can I use this runbook to scaffold Python projects and update Notion PROJECT DOCS select options?

Yes, this runbook applies to Python initiatives. It validates folder conventions, creates the Paperclip project, updates Notion PROJECT DOCS select options, and queues scaffold issue metadata for Python, TypeScript/Next.js, or Swift stacks.

What's the best way to ensure consistent naming and clone map synchronization when starting a new project?

The best way is to apply an execution policy that validates unique project codes, derives repository paths, notes required clone map edits for the nightly audit, and delivers a final initialization summary.

Why does my project initialization require Paperclip setup and Notion page batch-creation?

Project initialization requires Paperclip project creation and Notion batch-creation of Overview, Architecture, Roadmap, and Chat Log pages to keep documentation structured and satisfy execution policy requirements before scaffold generation.