architecture

You generate Architecture Decision Records (ADRs) in MADR format by providing an initial architectural prompt with relevant Epics and Features, which triggers the skill to produce the ADRs and a plan-context.md file for Claude Code.

Documenting architectural decisions and traceability is best handled by generating ADRs in MADR format and arc42 drafts, which explicitly maintain traceability between Epics, Features, ADRs, and the codebase to inform design choices.

To create a plan-context.md bridging requirements to technical designs, you provide an initial architectural prompt including relevant Epics and Features, which outputs the file to tie requirements to Claude Code-driven implementation.

Yes, the architecture skill enforces frontmatter metadata in its outputs, ensuring that the generated ADRs in MADR format and arc42 documentation maintain structured context and traceability for implementation.

Yes, you can use arc42 and MADR formats together by providing an architectural prompt, which generates both an arc42 draft and Architecture Decision Records to capture decisions and handoff context.

You need to generate a plan-context for Claude Code when you require a structured method to capture architectural decisions and hand off context from your requirements and technical designs to the implementation phase.