メニュー
Records architectural and implementation decisions. Use when a significant technical decision is made, a spec is modified, or an approach changes during implementation. Creates numbered decision records in .factory/decisions/.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generates structured requirements using EARS (Easy Approach to Requirements Syntax) notation. Use when the user is planning a feature, entering spec mode, or asking for requirements. Produces user stories with testable acceptance criteria.
Technology stack constraints and approved libraries. Auto-loaded when Droid is making technology choices, adding dependencies, or proposing architectural changes. Defines what frameworks, libraries, and patterns are allowed.
Guardrails for debugging and troubleshooting. Auto-loaded when Droid encounters errors, test failures, or build issues. Prevents context drift and tech stack swaps during error recovery.
| name | decision-log |
| description | Records architectural and implementation decisions. Use when a significant technical decision is made, a spec is modified, or an approach changes during implementation. Creates numbered decision records in .factory/decisions/. |
When a significant decision is made during development, record it.
Create a file in .factory/decisions/ with this format:
Filename: NNN-descriptive-name.md (e.g., 001-use-websockets-for-realtime.md)
Content:
# NNN: [Decision Title]
**Date:** YYYY-MM-DD
**Status:** Accepted | Superseded by NNN | Deprecated
**Relates to:** Requirement N (if applicable)
## Context
[What situation prompted this decision? 2-3 sentences.]
## Decision
[What was decided? 1-2 sentences.]
## Rationale
[Why this approach over alternatives? Key reasons.]
## Alternatives Considered
- [Alternative 1]: [Why rejected]
- [Alternative 2]: [Why rejected]
## Consequences
- [What changes as a result]
- [What trade-offs were accepted]
.factory/decisions/ for the latest number