project-setup

Automate project setup with constitution, templates, and initial git commit.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill project-setup-tasai-lab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-setup
Source: https://github.com/tasai-lab/fractal-dev-workflow/tree/main/skills/project-setup
Command: npx skills add https://github.com/tasai-lab/fractal-dev-workflow --skill project-setup-tasai-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automatically bootstraps a new project with a formal project constitution and templated structure to enforce a single source of truth and auditable governance.

Core Features & Use Cases

  • Constitution-driven setup: Places CLAUDE.md at project root and wires templates for governance.
  • Template provisioning: Creates docs/, prd.md, and tasks.md templates for requirements and planning.
  • Initial governance commit: Creates an initial git history capturing baseline rules and templates.

Quick Start

Place CLAUDE.md and template docs in the project root and run the setup to initialize governance artifacts.

Frequently Asked Questions about project-setup

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

FAQPage Schema
How do I automate project setup to install governance rules and documentation templates?

Automating project setup installs a project constitution and templates by placing CLAUDE.md at the root and creating docs with prd.md and tasks.md templates to enforce baseline governance.

What is a project constitution and when do I need templated documentation for onboarding?

A project constitution establishes a single source of truth for governance rules. You need templated documentation during onboarding or new repository initialization to capture baseline requirements and planning artifacts.

Do I need a CLAUDE.md file at the project root before running initial commit setup?

Yes, initial commit setup requires CLAUDE.md at the project root with name and description in frontmatter to wire governance rules and template provisioning correctly.

What's the best way to establish an auditable git history with baseline rules for a new repository?

Establishing an auditable git history with baseline rules is best achieved by initializing governance artifacts and performing an initial commit to capture the project constitution and templated docs.

Can I use project setup templates for requirements and planning without an existing git history?

Yes, project setup templates create docs with prd.md and tasks.md for requirements and planning, and perform an initial git commit to establish baseline governance history in new repositories.