Files
Ken Yasue e1ef10be6e feat: autonomous setup flow and per-feature doc reconciliation
- setup-project: run end-to-end without pausing for human approval between steps
- add-feature Step 8: reconcile all six persistent docs with each implemented feature
- AGENTS.md: align document-management principles with the new sync rule
- opencode.json: simplify permission config
2026-06-28 18:29:48 +02:00

3.1 KiB

description agent
Initial setup - automatically create the six persistent documents build

Initial Project Setup

This command automatically creates the project's six persistent documents without pausing for human feedback between steps.

How to Run

opencode
> /setup-project

Pre-Run Check

Check the files in the docs/ideas/ directory.

# Check
ls docs/ideas/

# If files exist
✅ Found docs/ideas/initial-requirements.md
   The PRD will be created based on its contents

# If no files exist
⚠️  No files found in docs/ideas/
    The PRD will be created from the project context

Procedure

Step 0: Read the Inputs

  1. Read all markdown files in docs/ideas/
  2. Understand their contents and use them as reference for creating the PRD

Step 1: Create the Product Requirements Document

  1. Follow the prd-writing skill (loaded automatically) to guide PRD creation
  2. Create docs/product-requirements.md based on the contents of docs/ideas/
  3. Flesh out the ideas raised during brainstorming:
    • Detailed user stories
    • Acceptance criteria
    • Non-functional requirements
    • Success metrics
  4. Run the skill's self-check checkpoints; if issues are found, fix them inline, then proceed immediately to the next step

All subsequent steps run automatically without waiting for human feedback.

Step 2: Create the Functional Design Document

  1. Follow the functional-design skill (loaded automatically)
  2. Read docs/product-requirements.md
  3. Create docs/functional-design.md following the skill's template and guide

Step 3: Create the Architecture Design Document

  1. Follow the architecture-design skill (loaded automatically)
  2. Read the existing documents
  3. Create docs/architecture.md following the skill's template and guide

Step 4: Create the Repository Structure Document

  1. Follow the repository-structure skill (loaded automatically)
  2. Read the existing documents
  3. Create docs/repository-structure.md following the skill's template

Step 5: Create the Development Guidelines

  1. Follow the development-guidelines skill (loaded automatically)
  2. Read the existing documents
  3. Create docs/development-guidelines.md following the skill's template

Step 6: Create the Glossary

  1. Follow the glossary-creation skill (loaded automatically)
  2. Read the existing documents
  3. Create docs/glossary.md following the skill's template

Completion Criteria

  • All six persistent documents have been created

Completion message:

"Initial setup is complete!

Documents created:
✅ docs/product-requirements.md
✅ docs/functional-design.md
✅ docs/architecture.md
✅ docs/repository-structure.md
✅ docs/development-guidelines.md
✅ docs/glossary.md

You are now ready to start development.

How to use going forward:
- Editing documents: just ask in normal conversation
  Examples: 'Add a new feature to the PRD', 'Review architecture.md'

- Adding features: run /add-feature [feature name]
  Example: /add-feature User authentication

- Document review: run /review-docs [path]
  Example: /review-docs docs/product-requirements.md
"