Defame1297
eae5c37b35
- Decision record covering 12 decisions from the factory integration grill - ADR-0008 (factory boundary: this repo is a provider, not a factory instance) - ADR-0009 (flat skill taxonomy with category metadata in frontmatter) - ADR-0010 (role skills in .agents/skills/; core/agents/ for subagent definitions) - Issue 0013 (LESSONS.md at repo root) - Issue 0014 (docs/spec/ living spec layer + VISION.md refactor) - ROADMAP Chunk 3 scope expanded: skills rebuild, new skills (session-handoff, governance-check, git-guardrails, write-adr), IaC/Gitea global optional - Per-skill process: implementation guidance Sections 4-5 and skills index referenced as starting point before web research and grilling - factory-research-gaps-conflicts.md marked superseded Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
2.4 KiB
0014 — docs/spec/ and VISION.md refactor
What to build
Introduce docs/spec/ as the living spec layer for this repo, and refactor docs/VISION.md to goals and intent only.
The distinction:
docs/VISION.md— purpose, goals, non-goals, long-term roadmap. Stable. Describes what the repo is for and where it is going.docs/spec/overview.md— current deployed state. What is working today. Updated in the same PR as any behavior change.docs/spec/architecture.md— current directory structure, install behavior, provider model, deployment pipeline, as-deployed. Replaces the architecture section of VISION.md.
1. Refactor VISION.md
Remove the Architecture section (directory structure diagram, content deployment model, governance layer description, provider model, this repo's own CLAUDE.md description, architectural decisions pointer). These describe current state, not intent. Move this content to docs/spec/architecture.md.
Keep in VISION.md: Purpose, Goals, Non-Goals, V1 Definition, Long-term Management Application vision.
2. Create docs/spec/overview.md
Current state snapshot: what chunks are complete, what is deployed, what works end-to-end. This is the "what does this repo do right now" document. Updated at the close of each chunk.
3. Create docs/spec/architecture.md
Current architecture: directory structure, install pipeline, provider adapter model, content deployment model, governance layer, CLAUDE.md two-tier model. Sourced from the VISION.md architecture section but written as current state, not design intent. Keep diagrams and tables.
4. Update CONTEXT.md docs convention
Add docs/spec/<slug>.md to the docs naming convention. Describe when spec files are updated (same PR as any behavior change).
5. Update CLAUDE.md key documents section
Add docs/spec/ to the list of documents to read at session start, alongside CONTEXT.md, VISION.md.
Acceptance criteria
docs/spec/overview.mdexists with current state of the repodocs/spec/architecture.mdexists with current architecture content (sourced from VISION.md architecture section)docs/VISION.mdcontains only Purpose, Goals, Non-Goals, V1 Definition, and Management Application vision- No content is lost — everything from the removed VISION.md sections appears in spec files
- CONTEXT.md docs convention references
docs/spec/ - CLAUDE.md key documents section references
docs/spec/
Blocked by
None.