codoop_flow.toml.example

# codoop-flow configuration (copy to codoop_flow.toml and edit).
# codoop-flow is a portable tool; these paths point at the TARGET project
# whose ticket pipeline you want to drive.

# Absolute path to the target git repository.
target_repo = "/path/to/your/codoop-project-repo"

# Where isolated per-ticket worktrees are created.
worktree_root = "~/codoop_tickets/worktrees"

# Ticket-document review flow: "strict" confirms each design phase;
# "one_pass" keeps grilling, then generates all ticket documents before one
# final promotion confirmation.
ticket_design_mode = "strict"

# Language for Skill replies and generated prose/documents. Use "auto" to
# follow the user's current language, or any BCP 47 language tag. Common
# examples: zh-CN, zh-TW, en, ja, ko, es, fr, de, pt-BR, it, ru, ar, hi.
output_language = "zh-CN"

# Usual professional context for live Skill conversations. Use `general` for a
# normal user or any unlisted industry. This never changes generated artifacts.
user_role = "product_manager"

# System project type -> real relative directory. Existing projects may use
# custom names; omit project types this repository does not own.
[project_paths]
backend = "backend"
web = "web"
desktop = "desktop"
mobile = "mobile"