arc42-spec

Translate development requirements into a 12-chapter arc42 Chinese specification document.

2|1|Updated Apr 27, 2026
One-click install
npx skills add https://github.com/nanzhipro/arc42-spec-skill --skill arc42-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: arc42-spec
Source: https://github.com/nanzhipro/arc42-spec-skill/tree/main/skills/arc42-spec
Command: npx skills add https://github.com/nanzhipro/arc42-spec-skill --skill arc42-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill translates a development requirement into a structured arc42-style Chinese technical specification document, ensuring traceability, consistency, and a clear blueprint for design, review, and implementation.

Core Features & Use Cases

  • Auto-generates all 12 arc42 chapters from a single requirement input, with phase-based validation and cross-chapter consistency checks.
  • Produces ADRs, risk registrations, and mapping tables to support architecture governance and reviews.
  • Supports different change types (new features, refactors, integrations, migrations, evolutions) through a repeatable, contract-driven workflow.

Quick Start

Generate a full arc42 specification document from the input requirement using a phase-driven workflow.

Frequently Asked Questions about arc42-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a complete arc42 specification document from a single development requirement?

To generate an arc42 specification, input your development requirement and the skill translates it into a structured 12-chapter Chinese technical specification document with cross-chapter consistency checks.

What is the best way to document architectural decisions and risks for a new software feature?

Documenting architectural decisions and risks is best handled by generating traceable ADRs and risk registration tables directly within the arc12 specification output.

Can I use arc42 specs for system migrations and integrations, or only new features?

Arc42 specs support various change types including new features, refactors, integrations, migrations, and architectural evolutions through a repeatable, contract-driven workflow.

Does this arc42 documentation skill require any specific frameworks or dependencies?

No specific dependencies are required. The skill independently processes your requirements and outputs a single Markdown specification file written to a determined path.

How are consistency and architectural governance maintained across the 12 arc42 chapters?

Consistency and architectural governance are maintained through phase gates and cross-chapter consistency checks during the phase-driven document generation workflow.

When do I need a formal arc42 specification for my software engineering project?

You need a formal arc42 specification when translating development requirements into a structured blueprint for design, review, and implementation to ensure traceability and consistency.