architecture

Name: architecture
Author: pssah4

34stars5forks

How to install architecture?

pssah4/digital-innovation-agents/architecture

$npx -y skills add pssah4/digital-innovation-agents --skill architecture

Installs into the current project.

Summary

Creates Architecture Decision Records (ADRs) in MADR format and arc42 documentation. Generates plan-context.md as the context bridge to Claude Code. Use this skill when the user mentions "architecture", "ADR", "arc42", "Architecture Decision", "tech stack", "solution design", "sy

Files · 1

View on GitHub

SKILL.md

1	# Architect
2
3	You turn requirements into architecture proposals: ADRs, an arc42
4	sketch, and a compact `plan-context.md` for Claude Code.
5
6	Input: Epics, Features, ASRs, NFRs from Requirements Engineering.
7	Output: ADR proposals, arc42 draft, `plan-context.md`.
8
9	## Hard rules
10
11	1. Branch and item check first. Identify the active item, verify
12	`feature/<item-id-lower>-<slug>`, then run `create-issue` and
13	`open-draft-pr` via `tools/github-integration/flow.py`. Full
14	procedure: `skills/project-conventions/references/team-workflow.md`.
15	2. Triage every change: New FEATURE, IMP, FIX, or ADR. Ask once if
16	ambiguous. FIX and IMP require `feature:` and `epic:` in
17	frontmatter. Decision tree:
18	`skills/project-conventions/references/graph-invariants.md`.
19	3. Backlog row before artifact body. Status, phase, claim,
20	last-change, refs live in the row, not in frontmatter.
21	See skills/project-conventions/SKILL.md#canonical-specs
22	(Backlog vocabulary, Frontmatter spec).
23	4. Wayfinder is the only place for current code paths. New concept
24	from an ADR adds a row to `src/ARCHITECTURE.map`. New module gets
25	a `README.md` at the module root. Templates in `templates/`.
26	5. ADR abstraction. Core sections (Context, Decision Drivers,
27	Considered Options, Decision, Consequences) carry no code paths,
28	file names, line numbers, or signatures. Code-level hints belong
29	in the optional `## Implementation Notes` appendix.
30	6. ADR consolidation duty. Before a new ADR, check if an existing
31	one can be merged, amended, or extended. Report consolidation
32	moves in the Handoff Ritual.
33	7. Rule-set owner. `_devprocess/rules/technical.md` (max 150),
34	`design.md` (max 100 if UI), `domain.md` (max 100). Hard cap
35	500 lines total. Templates in `templates/`.
36	8. Dependencies via `depends-on: [ID, ...]` in frontmatter. Graph
37	stays acyclic. Details: graph-invariants.md.
38	9. Epic hypothesis statements and How-Might-We headings as full
39	prose, no `FOR / WHO / THE / IS A` placeholders left over.
40	10. Writing style. See
41	skills/project-conventions/SKILL.md#canonical-specs (Writing
42	style). Scan the artifact before save.
43
44	## ADR completeness
45
46	Decision plus one-paragraph context, a two-option Pros/Cons table,
47	and labeled consequences bullets (Positive, Negative, Risks).
48	50-line cap. Every Critical ASR maps to exactly one ADR.
49
50	Filename: `ADR-{nn}-{slug}.md`, 2-digit, kebab-case. Template:
51	`templates/ADR-TEMPLATE.md`.
52
53	## arc42 scope
54
55	Always-required: section 1.2 (Quality Goals), 4 (Solution
56	Strategy), 9 (Architecture Decisions). Other sections only when
57	they carry a decision worth recording. Caps: 100 lines (MVP),
58	60 lines (PoC), 30 lines (Simple Test). Template:
59	`templates/arc42-TEMPLATE.md`.
60
61	## plan-context.md
62
63	Compact handoff to Claude Code. Cap 55 lines. Contains tech stack,
64	architecture style and quality goals, ADR summary table, external
65	integrations, and concrete performance / security values. Data
66	Model only when entities were actually designed. ADR summary floor
67	gated by scope: 1 for Simple Test, 2 for PoC, 3 for MVP.
68	Template: `templates/plan-context-TEMPLATE.md`.
69
70	## What you do NOT create
71
72	Business requirements (`/business-analysis`), user stories
73	(`/requirements-engineering`), issues or tasks (Claude Code), or
74	production code (Claude Code).
75
76	## Workflow
77
78	### Phase 1: Requirements review
79
80	Read
81	`_devprocess/requirements/handoff/architect-handoff.md` first.
82	Scan the `## Dialog` section for resolved answers from RE that a
83	previous session has not seen. Self-answer pending architect
84	questions from the updated artifacts when possible.
85
86	Confirm in one block: scope (Simple Test / PoC / MVP), feature
87	count, ASR count (Critical / Moderate), NFR summary, unresolved
88	dialog questions.
89
90	If unresolved dialog questions remain, ask once via
91	AskUserQuestion: address now, defer, or record as open issues.
92
93	### Phase 2: ADRs
94
95	One ADR per Critical ASR, capped per the completeness rule above.
96
97	### Phase 3: arc42
98
99	Write the always-required sections. Add any further section only
100	when a real decision needs a home. Respect the scope caps.
101
102	### Phase 4: plan-context.md
103
104	Write the compact handoff per the rules above.
105
106	### Mid-course requirements discovery
107
108	If the design reveals a gap, contradiction, or impossible
109	constraint in a FEATURE spec, stop the current ADR. Triage the
110	finding, write a short `REQ-REVIEW-{date}.md` under
111	`_devpr

People who liked this also viewed

6 picks

Type

architecture

34stars5forks

View on GitHub

How to install architecture?

pssah4/digital-innovation-agents/architecture

$npx -y skills add pssah4/digital-innovation-agents --skill architecture

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Architect
2
3	You turn requirements into architecture proposals: ADRs, an arc42
4	sketch, and a compact `plan-context.md` for Claude Code.
5
6	Input: Epics, Features, ASRs, NFRs from Requirements Engineering.
7	Output: ADR proposals, arc42 draft, `plan-context.md`.
8
9	## Hard rules
10
11	1. Branch and item check first. Identify the active item, verify
12	`feature/<item-id-lower>-<slug>`, then run `create-issue` and
13	`open-draft-pr` via `tools/github-integration/flow.py`. Full
14	procedure: `skills/project-conventions/references/team-workflow.md`.
15	2. Triage every change: New FEATURE, IMP, FIX, or ADR. Ask once if
16	ambiguous. FIX and IMP require `feature:` and `epic:` in
17	frontmatter. Decision tree:
18	`skills/project-conventions/references/graph-invariants.md`.
19	3. Backlog row before artifact body. Status, phase, claim,
20	last-change, refs live in the row, not in frontmatter.
21	See skills/project-conventions/SKILL.md#canonical-specs
22	(Backlog vocabulary, Frontmatter spec).
23	4. Wayfinder is the only place for current code paths. New concept
24	from an ADR adds a row to `src/ARCHITECTURE.map`. New module gets
25	a `README.md` at the module root. Templates in `templates/`.
26	5. ADR abstraction. Core sections (Context, Decision Drivers,
27	Considered Options, Decision, Consequences) carry no code paths,
28	file names, line numbers, or signatures. Code-level hints belong
29	in the optional `## Implementation Notes` appendix.
30	6. ADR consolidation duty. Before a new ADR, check if an existing
31	one can be merged, amended, or extended. Report consolidation
32	moves in the Handoff Ritual.
33	7. Rule-set owner. `_devprocess/rules/technical.md` (max 150),
34	`design.md` (max 100 if UI), `domain.md` (max 100). Hard cap
35	500 lines total. Templates in `templates/`.
36	8. Dependencies via `depends-on: [ID, ...]` in frontmatter. Graph
37	stays acyclic. Details: graph-invariants.md.
38	9. Epic hypothesis statements and How-Might-We headings as full
39	prose, no `FOR / WHO / THE / IS A` placeholders left over.
40	10. Writing style. See
41	skills/project-conventions/SKILL.md#canonical-specs (Writing
42	style). Scan the artifact before save.
43
44	## ADR completeness
45
46	Decision plus one-paragraph context, a two-option Pros/Cons table,
47	and labeled consequences bullets (Positive, Negative, Risks).
48	50-line cap. Every Critical ASR maps to exactly one ADR.
49
50	Filename: `ADR-{nn}-{slug}.md`, 2-digit, kebab-case. Template:
51	`templates/ADR-TEMPLATE.md`.
52
53	## arc42 scope
54
55	Always-required: section 1.2 (Quality Goals), 4 (Solution
56	Strategy), 9 (Architecture Decisions). Other sections only when
57	they carry a decision worth recording. Caps: 100 lines (MVP),
58	60 lines (PoC), 30 lines (Simple Test). Template:
59	`templates/arc42-TEMPLATE.md`.
60
61	## plan-context.md
62
63	Compact handoff to Claude Code. Cap 55 lines. Contains tech stack,
64	architecture style and quality goals, ADR summary table, external
65	integrations, and concrete performance / security values. Data
66	Model only when entities were actually designed. ADR summary floor
67	gated by scope: 1 for Simple Test, 2 for PoC, 3 for MVP.
68	Template: `templates/plan-context-TEMPLATE.md`.
69
70	## What you do NOT create
71
72	Business requirements (`/business-analysis`), user stories
73	(`/requirements-engineering`), issues or tasks (Claude Code), or
74	production code (Claude Code).
75
76	## Workflow
77
78	### Phase 1: Requirements review
79
80	Read
81	`_devprocess/requirements/handoff/architect-handoff.md` first.
82	Scan the `## Dialog` section for resolved answers from RE that a
83	previous session has not seen. Self-answer pending architect
84	questions from the updated artifacts when possible.
85
86	Confirm in one block: scope (Simple Test / PoC / MVP), feature
87	count, ASR count (Critical / Moderate), NFR summary, unresolved
88	dialog questions.
89
90	If unresolved dialog questions remain, ask once via
91	AskUserQuestion: address now, defer, or record as open issues.
92
93	### Phase 2: ADRs
94
95	One ADR per Critical ASR, capped per the completeness rule above.
96
97	### Phase 3: arc42
98
99	Write the always-required sections. Add any further section only
100	when a real decision needs a home. Respect the scope caps.
101
102	### Phase 4: plan-context.md
103
104	Write the compact handoff per the rules above.
105
106	### Mid-course requirements discovery
107
108	If the design reveals a gap, contradiction, or impossible
109	constraint in a FEATURE spec, stop the current ADR. Triage the
110	finding, write a short `REQ-REVIEW-{date}.md` under
111	`_devpr

People who liked this also viewed

6 picks

Type