chief-clancy 0.3.9 → 0.5.0

package/src/templates/.env.example.github

@@ -16,6 +16,11 @@ GITHUB_REPO=owner/repo-name
 # When an issue has a milestone, Clancy auto-creates milestone/{slug} from this branch.
 CLANCY_BASE_BRANCH=main
 
+# ─── Optional roles ─────────────────────────────────────────────────────────
+# Comma-separated list of optional roles to enable (e.g. planner)
+# Core roles (implementer, reviewer, setup) are always active.
+# CLANCY_ROLES=planner
+
 # ─── Loop ─────────────────────────────────────────────────────────────────────
 # Max tickets to process per /clancy:run session (default: 20)
 MAX_ITERATIONS=20
@@ -38,6 +43,10 @@ MAX_ITERATIONS=20
 # PLAYWRIGHT_STORYBOOK_PORT=6006
 # PLAYWRIGHT_STARTUP_WAIT=15
 
+# ─── Optional: Planner queue ─────────────────────────────────────────────────
+# Label for unrefined tickets that /clancy:plan should fetch (default: needs-refinement)
+# CLANCY_PLAN_LABEL=needs-refinement
+
 # ─── Optional: Notifications ──────────────────────────────────────────────────
 # Webhook URL for Slack or Teams notifications on ticket completion
 # CLANCY_NOTIFY_WEBHOOK=https://hooks.slack.com/services/your/webhook/url

package/src/templates/.env.example.jira

@@ -26,6 +26,11 @@ CLANCY_JQL_STATUS="To Do"
 # When a ticket has a parent epic, Clancy auto-creates epic/{key} from this branch.
 CLANCY_BASE_BRANCH=main
 
+# ─── Optional roles ─────────────────────────────────────────────────────────
+# Comma-separated list of optional roles to enable (e.g. planner)
+# Core roles (implementer, reviewer, setup) are always active.
+# CLANCY_ROLES=planner
+
 # ─── Loop ─────────────────────────────────────────────────────────────────────
 # Max tickets to process per /clancy:run session (default: 5)
 MAX_ITERATIONS=5
@@ -48,6 +53,10 @@ MAX_ITERATIONS=5
 # PLAYWRIGHT_STORYBOOK_PORT=6006
 # PLAYWRIGHT_STARTUP_WAIT=15
 
+# ─── Optional: Planner queue ─────────────────────────────────────────────────
+# Status name for backlog tickets that /clancy:plan should fetch (default: Backlog)
+# CLANCY_PLAN_STATUS="Backlog"
+
 # ─── Optional: Status transitions ────────────────────────────────────────────
 # Move tickets automatically when Clancy picks up or completes them.
 # Set to the exact status name shown in your Jira board column header.

package/src/templates/.env.example.linear

@@ -16,6 +16,11 @@ LINEAR_TEAM_ID=your-team-uuid
 # When an issue has a parent, Clancy auto-creates epic/{key} from this branch.
 CLANCY_BASE_BRANCH=main
 
+# ─── Optional roles ─────────────────────────────────────────────────────────
+# Comma-separated list of optional roles to enable (e.g. planner)
+# Core roles (implementer, reviewer, setup) are always active.
+# CLANCY_ROLES=planner
+
 # ─── Loop ─────────────────────────────────────────────────────────────────────
 # Max tickets to process per /clancy:run session (default: 20)
 MAX_ITERATIONS=20
@@ -38,6 +43,10 @@ MAX_ITERATIONS=20
 # PLAYWRIGHT_STORYBOOK_PORT=6006
 # PLAYWRIGHT_STARTUP_WAIT=15
 
+# ─── Optional: Planner queue ─────────────────────────────────────────────────
+# State type for backlog issues that /clancy:plan should fetch (default: backlog)
+# CLANCY_PLAN_STATE_TYPE=backlog
+
 # ─── Optional: Status transitions ────────────────────────────────────────────
 # Move issues automatically when Clancy picks up or completes them.
 # Set to the exact workflow state name shown in your Linear board column header.

package/src/templates/CLAUDE.md

@@ -53,6 +53,9 @@ When in doubt: "Is the primary deliverable a code change committed to this repo?
 Log completed tickets to `.clancy/progress.txt`:
 `YYYY-MM-DD HH:MM | TICKET-KEY | Summary | DONE`
 
+Planning entries use: `YYYY-MM-DD HH:MM | TICKET-KEY | PLAN | S/M/L`
+Approval entries use: `YYYY-MM-DD HH:MM | TICKET-KEY | APPROVE | —`
+
 ### Design context
 When a ticket description contains a Figma URL, fetch design context before implementing.
 Use the three-tier approach in order:
@@ -65,7 +68,7 @@ Figma URL must come from the ticket description only — never from CLAUDE.md or
 
 ### Visual checks
 After implementing a UI ticket, run a visual check before committing.
-Read .clancy/docs/PLAYWRIGHT.md to determine which server to use (Storybook or dev server).
+Read `.clancy/docs/PLAYWRIGHT.md` for the authoritative Playwright configuration (which server to use: Storybook or dev server). Use `.clancy/.env` only for ports and start commands as needed.
 Apply the decision rule against this ticket's description — route/page/screen/layout → dev server,
 component/atom/molecule/organism/variant/story → Storybook, ambiguous → dev server default.
 Start the server using health check polling (not sleep). Navigate to the relevant route or story.