بنقرة واحدة
adr
Create a new Architecture Decision Record (ADR) for a proposed feature or design change.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Create a new Architecture Decision Record (ADR) for a proposed feature or design change.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Bump version, generate changelog draft, tag, and deploy a release.
Create a feature branch, commit changes, push, and open a PR to main.
Check docs/ai/ spec files and ADRs for inconsistencies with the actual codebase. Report only, no modifications.
Check docs/ai/ spec files and ADRs for inconsistencies with the codebase, then fix all discrepancies.
Scan the codebase for security vulnerabilities. Check OWASP top 10, input validation, auth, crypto, and known BACKLOG security items.
Scan the project for refactoring opportunities, then fix them. No behavior/visual changes.
| name | adr |
| description | Create a new Architecture Decision Record (ADR) for a proposed feature or design change. |
| argument-hint | <title> |
| allowed-tools | Read, Glob, Grep, Bash(ls *), Write |
Create a new ADR document for: $ARGUMENTS
Determine next ADR number: List docs/ai/adr/ to find the highest existing number, then increment by 1.
Research the topic: Before writing, explore the codebase to understand the current state of the relevant area. Read related files, check existing ADR documents for context, and identify what currently exists vs what's missing.
Write the ADR at docs/ai/adr/{NNN}-{slug}.md using this format:
# ADR {NNN}: {Title}
## Status: Proposed
## Context
{Why is this needed? What's the current situation? What problems exist?}
## Decision
{The proposed design. Include:}
- Architecture / structure
- UI layout (ASCII diagrams if helpful)
- State management approach
- Implementation details
- Mobile considerations
## Considerations
{Trade-offs, open questions, alternative approaches considered}
## Future Extensions
{What could be built on top of this later}