diff --git a/.project/features/ci-status-refresh-on-main-coll.md b/.project/features/ci-status-refresh-on-main-coll.md
new file mode 100644
index 0000000..651cd82
--- /dev/null
+++ b/.project/features/ci-status-refresh-on-main-coll.md
@@ -0,0 +1,8 @@
+---
+slug: ci-status-refresh-on-main-coll
+status: backlogged
+logged: 2026-07-24
+---
+
+A CI job on the default branch regenerates STATUS.md post-merge in collaborative mode, so feature branches don't need to commit regenerated report files (PR noise).
+Why: collaborative mode makes committed STATUS.md churn in every PR; merge=ours mitigates conflicts but not diff noise — post-merge CI regeneration keeps main's report fresh without branch commits.
diff --git a/.project/features/delegate-model-routing.md b/.project/features/delegate-model-routing.md
new file mode 100644
index 0000000..5f86537
--- /dev/null
+++ b/.project/features/delegate-model-routing.md
@@ -0,0 +1,8 @@
+---
+slug: delegate-model-routing
+status: backlogged
+logged: 2026-07-24
+---
+
+Configurable model routing for /ardd-implement's delegated worktree runs: a delegate_model constitution frontmatter field, either a single tier alias or a complexity map keyed by the tasks file's complexity: stamp, resolved to a model: override on the Agent dispatch.
+Why: subagents start with fresh context, so the delegation boundary is the one place model routing costs no prompt cache (per-skill session routing was investigated and rejected — per-model caches make it net-negative for frequent skills). Prefer tier aliases over model names to survive model churn; default asymmetric — routing complex files up matters more than routing simple ones down. Depends on plan-time-complexity-stamps for the map form.
diff --git a/.project/features/plan-time-complexity-stamps.md b/.project/features/plan-time-complexity-stamps.md
new file mode 100644
index 0000000..82e68da
--- /dev/null
+++ b/.project/features/plan-time-complexity-stamps.md
@@ -0,0 +1,8 @@
+---
+slug: plan-time-complexity-stamps
+status: backlogged
+logged: 2026-07-24
+---
+
+At tasks-file generation time, /ardd-plan stamps a complexity: simple|moderate|complex field into each tasks file's frontmatter, reviewed and correctable at the plan approval checkpoint.
+Why: plan time is when full context exists to predict how much judgment implementation will need; the stamp is the on-disk routing signal for model selection at implement dispatch (see implement-dispatch-model-routing). Enum lands in lint-project.sh in the same commit.