Write a concrete architecture spec, design doc, or tech spec for an already chosen software architecture or technical direction. Trigger when the user asks to write a design doc, tech spec, architecture spec, implementation spec, or phrases like "собери design doc", "напиши tech spec", "оформи архитектуру в документ", "сделай инженерный спек", or similar. The document must act as an engineering contract for implementation: define the goal, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, observability, validation plan, and open questions. Keep it concrete and implementation-oriented. Do not produce corporate filler, vague future-proofing, or decorative sections with no execution value. Do not use for architecture option comparison, generic brainstorming, product requirements docs, or a detailed milestone plan after the design is already fixed.
Install with
Claude CodeCodexCursorGitHub CopilotGemini CLI
Supported by the Atlas install prompt. Skill-specific requirements vary.
Skill stats
Skills1CategoryContent & writingStars0
About this skill
Write a concrete architecture spec, design doc, or tech spec for an already chosen software architecture or technical direction. Trigger when the user asks to write a design doc, tech spec, architecture spec, implementation spec, or phrases like "собери design doc", "напиши tech spec", "оформи архитектуру в документ", "сделай инженерный спек", or similar. The document must act as an engineering contract for implementation: define the goal, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, observability, validation plan, and open questions. Keep it concrete and implementation-oriented. Do not produce corporate filler, vague future-proofing, or decorative sections with no execution value. Do not use for architecture option comparison, generic brainstorming, product requirements docs, or a detailed milestone plan after the design is already fixed.
Quick start
Copy the install prompt. Use the green button above this README.
Send it to your agent. Paste it into your coding agent’s chat and send.
Review the setup. Your agent checks the skill’s instructions, requirements, and installation scope.
Write a concrete architecture spec, design doc, or tech spec for an already chosen software architecture or technical direction. Trigger when the user asks to write a design doc, tech spec, architecture spec, implementation spec, or phrases like "собери design doc", "напиши tech spec", "оформи архитектуру в документ", "сделай инженерный спек", or similar. The document must act as an engineering contract for implementation: define the goal, non-goals, invariants, interfaces, data flow, dependencies, failure modes, rollout plan, observability, validation plan, and open questions. Keep it concrete and implementation-oriented. Do not produce corporate filler, vague future-proofing, or decorative sections with no execution value. Do not use for architecture option comparison, generic brainstorming, product requirements docs, or a detailed milestone plan after the design is already fixed.
About this listing
Category
Content & writing
Reported license
Not specified
Listing language (estimated)
English
Review status
Not individually reviewed
Agent compatibility
Atlas installation supports Claude Code, Codex, and Cursor. Skill-specific dependencies and features are checked during setup.
Claude Code
Codex
Cursor
GitHub Copilot
Gemini CLI