project-setuplisted

# Project Setup Skill Set up a new project with a standardized, agent-legible structure. ## When to Use - User asks to create/set up a new project - User has a folder with source material (transcript, article, notes) to bootstrap from - User wants a consistent starting structure for a new repo ## Inputs | Input | Required | Description | |-------|----------|--------------| | Project name | Yes | Directory name (kebab-case, e.g., `cyber-readiness`) | | Project path | Yes | Usually `~/projects/[project-name]` | | Purpose | Yes | One sentence describing what the project is | | Source material | No | Transcript, article, or notes to derive context from | | Tech stack | No | If known; often TBD at setup time | ## Process ### 1. Gather Context If source material exists: - Read and analyze it - Extract: purpose, key concepts, stakeholders, constraints, open questions - Identify potential phases/milestones If no source material: - Ask user for: purpose, key context, any known constraints ### 2. Create Directory Structure ``` [project-name]/ ├── CLAUDE.md ├── scratchpad.md ├── .gitignore ├── .claude/ │ ├── agents/ # Project-specific agents (empty) │ └── skills/ # Project-specific skills (empty) └── docs/ ├── INDEX.md ├── plans/ │ └── [project-name]-plan.md ├── sessions/ # Session history (empty) ├── research/ # Research outputs (empty) └── Archive/ # Obsolete docs (empty) ``` ### 3. Configure .mcp.json Allowlist (