docs(adr): three new ADRs — ADR-028 App Init, ADR-029 Skills, ADR-030 Agent Pipeline

[seanspeaks]

Summary

Three new proposed ADRs that fill gaps identified after reviewing the consolidated ADR register (#621) and the in-production adopter skill layer.

Rebased and relocated to the numbered register per ADR-014 (which merged as part of #617 → #621 while this PR was drafting). Files were originally at docs/architecture/ADR-*.md; they now live at the assigned numbered slots. Content is unchanged from the original drafts. Note: ADR-027 is reserved for Integration Versioning, which is in-flight in a separate open PR.

The three ADRs

ADR-028: App Init (129 lines). Proposes what frigg init should produce: a named Project Template (minimal / production / agent-enabled) plus an interactive interview that scaffolds plugin selections, initial Core Extensions, an L4 ontology seed, an optional reference integration, and CI wiring. Closes the gap flagged in issue #595 and repurposes the vestigial --template flag.

ADR-029: Skills (131 lines). Introduces skills as a defined layer with four subtypes:

Subtype	Example content	Loaded by
Knowledge	L3/L4 ontology fragment	Any agent via skills: frontmatter
Contract	JSON Schema + template	Producer and consumer agents in a pipeline
Runbook	Scripts, templates, step-by-step procedure	User or agent per-invocation
Recipe	Multi-phase orchestration with embedded knowledge	User or top-level agent

Documents the user-invocable: false flag for sub-agent-only skills, and skill-to-agent preloading via skills: frontmatter as a declarative alternative to the ADR-025 Agent Harness hook.

ADR-030: Agent Pipeline (137 lines). Codifies the scope → build → review multi-agent pattern observed in production. Model tiering per phase (opus for creative and skeptical work, sonnet for mechanical build), read-only adversary via disallowedTools: Write, Edit, typed handoffs via contract-skill schemas, EARS acceptance criteria threading requirement to test through the pipeline.

Distinguishes cleanly from the harness ADR: the harness grounds an individual agent's session; the pipeline composes multiple agents.

How they interact with the merged set

                                      ADR-028
                                      (scaffolds at
                                       project creation)
                                          │
                                          ▼
     CAPABILITIES  ONTOLOGY  PLUGINS  EXTENSIONS  TEMPLATES
       (020)       (021)     (016)    (015/017/     (023)
                                       018/019)
          │             │        │        │           │
          └─────────────┴────────┴────────┴───────────┘
                                  │
                                  ▼
                          ┌───────────────┐
                          │   ADR-029     │  ← agents preload via
                          │  4 subtypes   │    skills: frontmatter
                          └───────┬───────┘
                                  │
                        ┌─────────┴─────────┐
                        ▼                   ▼
                    ADR-025             ADR-030
                Agent Harness       Agent Pipeline
                (grounds one)       (composes many)

Style bar

• Each ADR under 200 lines (129 / 131 / 137)
• One Mermaid diagram each
• One working code example each
• Zero em-dashes, "load-bearing", "first-class", rhetorical contrast patterns
• No references to private repos
• Follows the ADR-014 register convention: # ADR-NNN: Title heading, Status / Date / Deciders metadata block, standard section structure

Test plan

• Read all three in order: 028 → 029 → 030
• Verify cross-references resolve to the correct numbered slots (015–026 plus 028–030)
• Confirm the skill-subtype taxonomy in ADR-029 matches how you think about knowledge vs contract vs runbook vs recipe
• Confirm ADR-030 and ADR-025 separation lands, or ask for a merge into one ADR
• Confirm ADR-028 scope is right (proposes frigg init interview flow; does NOT propose the exact contents of the agent-enabled template)

Notes

• Draft. Move to ready-for-review when the shape is settled.
• No release / prerelease labels; docs-only.
• Two naming decisions worth calling out:
  • "Contract skill" (not "Definition skill", to avoid collision with static Definition)
  • "Agent Pipeline" (not "Multi-Agent Workflow", shorter and matches sequential composition)
• ADR-027 slot reserved for Integration Versioning in a separate PR.

---

Generated by Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud