Phuriwaj

PKM SDLC Note Templates

Planted 20 days ago

PKM SDLC Note Templates

Building a system for Claude Code to create and maintain software requirement/spec/test-case notes with V-model traceability — frontmatter-linked documents that form a live RTM when queried via zk.

Current Focus

Design phase complete. Next: extend frontmatter schema, create 4 core document templates, build update-sdlc skill.

Open Tasks

  • Extend skill-config.yaml: add level, verified_by, verifies, status fields to SDLC doc type
  • Create template: Business Requirement (BR)
  • Create template: Functional Requirement (FR)
  • Create template: Technical Specification (TS)
  • Create template: Test Case (TC)
  • Build update-sdlc skill (separate from update-status) for:
    • Creating new SDLC notes with correct frontmatter and auto-linking
    • Generating RTM/V-model maps on demand via zk queries
  • Init .zk/ notebook in first project directory
  • Test gap-analysis query: requirements without linked test cases

Key Decisions / Insights

People

None yet.

Progress Log

2026-05-14

Follow-up conversation on AI-native SD note-taking confirmed the three document category model: Knowledge (evergreen, compounds), Process artifacts (relational — V-model/RTM, value is in links not content alone), Time-anchored (requirements versioned — decay when superseded). Key insight reinforced: V-model and RTM are not documents to maintain — they are relationship maps. RTM is a flattened view of frontmatter links; generate on demand via zk. The update-sdlc skill should handle both creation (with auto-linking) and map generation. Folder structure for projects: efforts/on/project-slug/ with subdirs requirements/, specs/, domain/, api/, data/, tests/, maps/. LaTeX decision settled: stay with .md throughout; use LaTeX math syntax inside markdown only where equations are needed.

2026-05-13

Designed in conversation “Note Taking - For AI Native SD”. Confirmed effort notes stay as lifecycle trackers (current focus, open tasks, progress log) — no changes to existing format. New SDLC document templates need four additional frontmatter fields: level (BR/FR/TS/TC), verified_by (link to test case), verifies (link to requirement), status (draft/approved/implemented/verified). The update-sdlc skill will use zk queries to surface the V-model as a live view rather than a static document.

Week of 2026-W20 (Mon 12 – Sun 17 May)

Full design completed across May 13–14. Three document categories established: Knowledge (evergreen), Process artifacts (relational — V-model/RTM), Time-anchored (requirements versioned). Four new frontmatter fields confirmed. RTM and V-model generated on demand via zk queries — not maintained manually. Separate update-sdlc skill to be built (distinct from update-status). Markdown confirmed as the universal format (LaTeX only for formal PDF exports). zk dual-notebook pattern decided: ~/notes/ for personal PKM, ~/projects/<project>/.zk/ for software docs.

Status: 🟡 Design complete — schema extension and templates not yet built.

Open tasks (W21):

  • Extend skill-config.yaml with SDLC fields: level, verified_by, verifies, status
  • Create 4 SDLC document templates: BR, FR, TS, Test Case
  • Build update-sdlc skill for Claude Code
  • Install zk on phuriwajr-dev and init ~/notes/.zk/config.toml