project-init

Scaffolds SynthesisFlow directory structure with docs/specs and docs/changes folders for spec-driven development.

Updated Jul 13, 2024
One-click install
npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill project-init-reading-advantage-thailand
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: project-init
Source: https://github.com/Reading-Advantage-Thailand/codecamp-advantage/tree/main/.claude/skills/project-init
Command: npx skills add https://github.com/Reading-Advantage-Thailand/codecamp-advantage --skill project-init-reading-advantage-thailand

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Setting up a consistent spec-driven development structure from scratch is error-prone and inconsistent across projects. This Skill automates the creation of the SynthesisFlow directory layout so teams start with the same conventions for specifications and change proposals. ## Core Features & Use Cases - Directory Scaffolding: Creates docs/specs/ for approved specifications and docs/changes/ for proposed changes via a single bash script. - Existing Documentation Detection: Automatically detects markdown files in an existing docs/ directory and recommends the project-migrate skill instead, preventing accidental misuse. - Idempotent Execution: Safe to run multiple times without overwriting or deleting existing directories. - Use Case: When starting a new repository that will follow spec-driven development, run the init script to instantly establish the standard docs/specs and docs/changes structure before authoring your first specification. ## Quick Start Initialize the SynthesisFlow directory structure in my current project so I can begin writing specifications.

Frequently Asked Questions about project-init

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

FAQPage Schema
How do I set up a spec-driven development folder structure?▼

Run the init-project.sh script with bash, optionally passing -d to specify a target directory. It creates docs/specs for approved specifications and docs/changes for proposed changes, establishing the standard SynthesisFlow layout.

What is the difference between project-init and project-migrate?▼

Use project-init for new projects or empty docs directories that only need the basic structure. Use project-migrate when existing markdown documentation must be cataloged, relocated with git history preserved, and updated with compliant frontmatter.

Can I run the initialization script multiple times safely?▼

Yes, the script is idempotent. It uses mkdir -p, so existing directories are left untouched and no files are overwritten or deleted on repeated runs.

What happens if my docs folder already has markdown files?▼

The script counts markdown files in docs/ outside specs/ and changes/, warns you, and recommends the project-migrate skill instead. You can confirm to continue with basic initialization or cancel.

Does the script create specification files automatically?▼

No, it only creates the docs/specs and docs/changes directories. Content such as specifications, proposals, and RETROSPECTIVE.md must be added manually or through other skills like spec-authoring.