Files
DonchitosandClaude Opus 5.5 be8993bbc5 Release 1.1.3 — long skills keep their later steps
Fix release for 1.1.2: the 14 longest skills keep their later phases
after a compaction, a question nobody answered is never taken as an
answer, settings read the same from a subfolder, the commit check works
for a project in a subfolder of a larger repository, every skill opens
with a title, and the shipped allow rules no longer approve deleting a
branch or writing files without asking. Details in CHANGELOG.md; upgrade
steps in UPGRADING.md (v1.1.2 → v1.1.3).

Refs #83
Refs #133

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0185en4t76fPn7315q4c3nko
2026-10-08 17:52:48 +11:00

28 lines
1.1 KiB
YAML

# CCGS project configuration — single source of truth for project settings.
# See .claude/docs/effects-map.md for full schema.
schema_version: 1
framework:
version: 1.1.3
last_upgraded: 2026-09-25
# NOTE: this template ships with no `modes:` block, and the six knobs below must
# never be added to one.
#
# `/start` DOES add `modes.rigor` and `modes.automation` here — that is its job,
# and a `modes:` block containing those two is the expected state of a configured
# project, not a mistake.
#
# What must stay absent is the six knobs `modes.rigor` FRONTS:
# `modes.review_mode`, `modes.workflow`, `docs.density`, `qa.level`,
# `modes.story_granularity` and `team.size`. Seeding any of them in this file
# pins that value and shadows the rigor expansion, so `/start` asking "what are
# you building?" would stop changing anything. `/start` Phase 3c documents the
# same rule for the file it writes.
#
# Per-developer preferences belong in `project.local.yaml` (gitignored), not
# here. `/settings --local <key>=<value>` writes there; `/settings <key>=<value>`
# edits this file. See `.claude/docs/config-resolution.md` for the full
# precedence order.