Decisions
- Which categories to use? → skills, agents, hooks, features, code
- Subfolders per category or tags in frontmatter? → Subfolders chosen
User Tasks
Summary
Split proposals into typed categories so they’re easier to review and route.
Problem / Motivation
All proposals currently land in a flat vault/90_inbox/proposals/ folder. As the system grows, different types of proposals need different review approaches — a skill suggestion is quick to evaluate, a codebase architecture change needs deeper thought, and a CLAUDE.md update affects all future sessions. A flat list makes it hard to prioritize and batch-review.
Proposed Solution
Categorize proposals by type, either via subfolders or frontmatter tags. Each category has a clear scope and review expectation.
Candidate categories:
| Category | Scope | Example |
|---|---|---|
| skill | New or improved slash command | ”Add a /health skill” |
| agent | New sub-agent definition | ”Create a vault-cleanup agent” |
| rule | New or updated path-scoped rule | ”Add rules for 20_knowledge/“ |
| hook | New hook script | ”Pre-commit hook for protected files” |
| claude-config | CLAUDE.md, settings.json, or memory changes | ”Add tone rules to CLAUDE.md” |
| vault | Vault structure, templates, dashboards | ”Reorganize 90_inbox/“ |
| codebase | src/ architecture, patterns, dependencies | ”Use dependency injection pattern” |
| workflow | Process changes, how we work | ”Change feature review flow” |
Open Questions
1. Category List
Question: Which categories to use?
| Option | Description |
|---|---|
| A) All 8 above | Full granularity from the start |
| B) Simplified (4) | skill, config, vault, codebase — merge smaller ones |
| C) Start with tags only | No subfolders, just a category: field in frontmatter |
Recommendation: Option C — least structural overhead, easy to recategorize later.
Decision: Simplified set — skills, agents, hooks, features, code.
2. Storage Approach
Question: Subfolders per category or tags in frontmatter?
| Option | Description |
|---|---|
| A) Frontmatter tags | Keep flat folder, add category: skill to frontmatter. Filter via search. |
| B) Subfolders | proposals/skill/, proposals/vault/, etc. Visual separation in Obsidian. |
| C) Prefix naming | proposal-skill-xxx.md, proposal-vault-xxx.md. No folder change. |
Recommendation: Option A — proposals are temporary (approve/reject/defer), so heavy folder structure isn’t worth it.
Decision: Option B (subfolders) — chosen for visual clarity and simpler routing logic.
Phase Overview
| Phase | Description | Status |
|---|---|---|
| Phase 1 | Add category field to proposal template and existing proposals | done |
| Phase 2 | Update workflow docs and dashboard filtering | done |
Phase 1: Categorize Proposals —
Goal: Add a category field to the proposal template and backfill existing proposals.
| File / Feature | Details | Owner | Status |
|---|---|---|---|
vault/_templates/proposal.md | Add category: to frontmatter | opus | — |
| Existing proposals | Backfill category on current proposals | opus | — |
Phase 2: Workflow Integration —
Goal: Make categories visible in review workflow.
| File / Feature | Details | Owner | Status |
|---|---|---|---|
vault/00_system/docs/workflow.md | Document category types in Proposals section | opus | — |
| Review dashboard | Group proposals by category if useful | mv | — |
Test
Manual tests
| Test | Expected | Actual | Last |
|---|---|---|---|
| … | … | pending | - |
AI-verified tests
| Scenario | Expected behavior | Verification method |
|---|---|---|
| … | … | … |
E2E tests
| Scenario | Assertion |
|---|---|
| … | … |
Integration tests
| Component | Coverage |
|---|---|
| … | … |
Unit tests
| Component | Tests | Coverage |
|---|---|---|
| … | … | … |
History
| Date | Event | Details |
|---|---|---|
| 2026-03-04 | Created | Based on observation that flat proposal folder doesn’t scale |
| 2026-03-12 | Implemented | Subfolder approach chosen (skills, agents, hooks, features, code). All docs updated. |
References
- FR-066 (Self-Improving System) — proposals are the output of self-improvement
- FR-028 (Feature Workflow Automation) — automation could auto-categorize proposals