メニュー
Architecture proposals with trade-off analysis, alternatives matrix, and decision rationale. Trigger: design architecture, propose solution, evaluate alternatives, create ADR.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Create or update a CONSTITUTION.md that defines project governance — establishes coding standards, quality gates, TDD policy, review requirements, and non-negotiable development principles with versioned amendment tracking. Use when defining project rules, setting up coding standards, establishing quality gates, configuring TDD requirements, or creating non-negotiable development principles.
Create a feature specification from a natural language description — generates user stories with Given/When/Then scenarios, functional requirements (FR-XXX), success criteria, and a quality checklist. Use when starting a new feature, writing a PRD, defining user stories, capturing acceptance criteria, or documenting requirements for a product idea.
Generate Gherkin .feature files from requirements before implementation — produces executable BDD scenarios with traceability tags, computes assertion integrity hashes, and locks acceptance criteria for test-driven development. Use when writing tests first, doing TDD, creating test cases from a spec, locking acceptance criteria, or setting up red-green-refactor with hash-verified assertions.
Validate cross-artifact consistency — checks that every spec requirement traces to tasks, plan tech stack matches task file paths, and constitution principles are satisfied across all artifacts. Use when running a consistency check, verifying requirements traceability, detecting conflicts between design docs, or auditing alignment before implementation begins.
Generate a technical design document from a feature spec — selects frameworks, defines data models, produces API contracts, and creates a dependency-ordered implementation strategy. Use when planning how to build a feature, writing a technical design doc, choosing libraries, defining database schemas, or setting up Tessl tiles for runtime library knowledge.
Generate quality checklists that validate requirements completeness, clarity, and consistency — produces scored checklist items linked to specific spec sections (FR-XXX, SC-XXX). Use when reviewing a spec for gaps, doing a requirements review, verifying PRD quality, auditing user stories and acceptance criteria, or gating before implementation.
| name | architecture-design |
| author | JM Labs (Javier Montaño) |
| description | Architecture proposals with trade-off analysis, alternatives matrix, and decision rationale. Trigger: design architecture, propose solution, evaluate alternatives, create ADR. |
| allowed-tools | ["Read","Write","Edit","Glob","Grep","Bash","Agent"] |
Evidence-based architecture proposals with explicit trade-offs and alternatives.
Architecture is the art of trade-offs, not the application of best practices. Every choice has a cost — make it visible.
Before designing, map the constraints:
| Constraint Type | Examples |
|---|---|
| Technical | Existing stack, data formats, API contracts, performance SLAs |
| Organizational | Team size, skill distribution, deployment cadence |
| Business | Timeline, budget, compliance requirements |
| Operational | Uptime requirements, monitoring capability, incident response |
Generate at least 3 viable options:
For each option, evaluate:
| Dimension | Score (1-5) | Notes |
|---|---|---|
| Complexity | How hard to implement and maintain | |
| Risk | What could go wrong | |
| Time to implement | Calendar time to production | |
| Scalability | How well it handles growth | |
| Maintainability | How easy to modify in 6 months | |
| Team fit | Does the team have the skills? |
Document the decision as an ADR:
Generate as needed:
