Create template notes for new types (review, architecture, user-story, sop, convention) #185

New issue

Open

opened 2026-03-28 01:57:21 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-28 01:57:21 +00:00

Contributor

Type

Task

Scope

Create 5 new template notes in pal-e-docs via MCP tools. Each template defines the required structure for its note type, following the axiom: type → template → SOP → hook.

template-review: Verdict heading (h2), sections for each review dimension (Template Completeness, Traceability, File Targets, Acceptance Criteria, Blast Radius, Recommendation). Tag conventions: review + verdict tag.

template-architecture: Three-variant structure (domain=erDiagram, dataflow=sequenceDiagram, deployment=graph TB). Required: Mermaid diagram block, Components table, Decisions list. Slug convention: arch-{facet}-{project}.

template-user-story: Role, Key, Want, So-That, Acceptance Criteria, Success Metric, Related Architecture. Slug convention: story-{project}-{key}.

template-sop: Steps (ordered), Related SOPs, Related Conventions. Every SOP must be actionable — steps, not prose.

template-convention: Rule Statement, Rationale, Examples, Enforcement (hook name if exists), Related.

Acceptance Criteria

template-review note exists with correct structure
template-architecture note exists with three-variant documentation
template-user-story note exists with structured fields
template-sop note exists with required sections
template-convention note exists with required sections
All templates have note_type=template, status=active, project=pal-e-agency

project-pal-e-agency
forgejo_admin/claude-custom #180 -- parent spike

### Type Task ### Scope Create 5 new template notes in pal-e-docs via MCP tools. Each template defines the required structure for its note type, following the axiom: type → template → SOP → hook. **template-review**: Verdict heading (h2), sections for each review dimension (Template Completeness, Traceability, File Targets, Acceptance Criteria, Blast Radius, Recommendation). Tag conventions: review + verdict tag. **template-architecture**: Three-variant structure (domain=erDiagram, dataflow=sequenceDiagram, deployment=graph TB). Required: Mermaid diagram block, Components table, Decisions list. Slug convention: arch-{facet}-{project}. **template-user-story**: Role, Key, Want, So-That, Acceptance Criteria, Success Metric, Related Architecture. Slug convention: story-{project}-{key}. **template-sop**: Steps (ordered), Related SOPs, Related Conventions. Every SOP must be actionable — steps, not prose. **template-convention**: Rule Statement, Rationale, Examples, Enforcement (hook name if exists), Related. ### Acceptance Criteria - [ ] template-review note exists with correct structure - [ ] template-architecture note exists with three-variant documentation - [ ] template-user-story note exists with structured fields - [ ] template-sop note exists with required sections - [ ] template-convention note exists with required sections - [ ] All templates have note_type=template, status=active, project=pal-e-agency ### Related - `project-pal-e-agency` - `forgejo_admin/claude-custom #180` -- parent spike