Forge setup questionnaire

Answer these questions to configure Forge for your project. The setup wizard (Cursor rule or manual) uses these answers to determine scaling tier, active Versonas, ceremony weight, and directory structure.

1. Team size

How many people contribute to this project?

• [ ] Solo (1 person, all hats)
• [ ] Small team (2–5 people)
• [ ] Team (5–12 people)
• [ ] Multi-team (12+ people)

2. Roles and hats

Which hats are worn by dedicated people vs shared?

For solo: all hats are shared. For small team: likely 1–2 dedicated, rest shared.

3. Product stage

What stage is the product in?

• [ ] PoC — validating a hypothesis
• [ ] MVP — delivering minimum viable value
• [ ] Growth — iterating on a launched product
• [ ] Mature — maintaining and extending a stable product

4. Active disciplines

Which discipline families are relevant to this project? (Select all that apply)

• [ ] Engineering — SE, Architecture, DevOps, Testing, Frontend, Mobile, Embedded/IoT
• [ ] Data — Big Data, Data Science
• [ ] Product — BA, UX, Marketing, Customer Success
• [ ] Governance — PM
• [ ] Security (cross-cutting)
• [ ] Compliance (cross-cutting)

Within Engineering, which sub-disciplines apply?

• [ ] Software Engineering (always)
• [ ] Software Architecture
• [ ] DevOps
• [ ] Testing
• [ ] Frontend
• [ ] Mobile
• [ ] Embedded / IoT

5. Iteration length

• [ ] 1 week (default — fast feedback)
• [ ] 2 weeks (more exploratory work, larger scope)

6. Ceremony weight

How formal should ceremonies be?

• [ ] Light — solo or very small team; minimal ceremony; AI Versonas primary
• [ ] Standard — small to medium team; regular ceremonies; mix of AI and human Versonas
• [ ] Formal — larger team or regulated domain; full ceremony set; stakeholder sign-offs; compliance Versona

7. CI/CD maturity

What is your current CI/CD state?

• [ ] None — no automated pipeline
• [ ] Basic — lint + build on push
• [ ] Standard — lint + build + test on PR
• [ ] Advanced — full pipeline with quality gates, security scans, deployment automation

8. AI comfort level

How comfortable is the team with AI-assisted development?

• [ ] New — first time using AI coding tools
• [ ] Exploring — some experience, learning
• [ ] Practiced — regular AI tool usage, understands limitations
• [ ] Advanced — deep AI integration, custom agents, MCP tools