Project Workspaces
Create a local workspace configuration for this project.
Jira integration is optional. You can connect or sync Jira later. Leave these fields blank to create the project without Jira.
Jira connection
No Jira connections configured. Add a connection to enable Jira sync.
Alternative names this project may be referred to by. Used later for project search, project-scoped chat, and matching natural language references to the right workspace. Add one alias per line.
Product summary describes the product to a stakeholder. Architecture summary describes the system to a developer. Context summary describes the current project situation to an AI assistant.
What the product does, who it helps, and what value it provides.
How the system is built: stack, app structure, integrations, persistence, and technical principles.
Current project focus, constraints, priorities, recent decisions, and anything the AI should keep in mind right now.
Repository details are currently used as project context only. GitHub connection, repository selection, PR linking, and check status will be added in later phases.
Default labels are used for task organization and traceability. They are also applied to Jira issues if Jira is configured. Default checks are validation commands for implementation quality.
Labels that should usually be applied to generated tasks for this project. Use broad, stable labels like the project name or workflow source. Avoid task-specific labels like bug, frontend, urgent, or phase names unless they apply to almost every task.
Commands that should usually be run before implementation handover or PR review. These will later be included in implementation handoff prompts and review expectations.
Human Coder Adviser keeps the current implementation-advice behavior. Vibe-Coder keeps normal chat focused on product and UX decisions while leaving implementation detail for drafts and handoffs.