القائمة
Archive a completed and verified spec. Moves it from active specs to the docs archive, updates the spec registry. Use after spec-verify passes.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Index of the kiro-rails engineering toolbox in this repo: every review command, spec workflow, subagent, and steering rule, with when to use each. Load this to decide which review or workflow to run, or to discover what kiro-rails offers. Routing only - each entry points at its own command, skill, or agent.
Security incident response, breach containment, evidence preservation, and recovery verification. Use when a breach, compromise, or security incident is detected or suspected.
Interactive guide to kiro-rails review prompts, agents, and tools. Explains which review to run, when, and why. Invoke with /review-guide or ask "what reviews should I run?", "which prompt?", or "how do I audit?".
Authentication, SSO, OAuth, OIDC, login, redirect, token implementation patterns. Use when implementing auth flows, login pages, token refresh, SSO integration, or redirect handling.
Implement a proposed spec. Reads the spec folder, follows the task checklist, writes code using TDD. Use after spec-propose is complete and approved.
Propose a new feature or change. Creates a structured spec folder with proposal, requirements, design, and tasks before any code is written. Use when starting new work.
| name | spec-archive |
| description | Archive a completed and verified spec. Moves it from active specs to the docs archive, updates the spec registry. Use after spec-verify passes. |
Archive a completed spec after it passes verification.
.kiro/specs/<name>/ to docs/architecture/specs/<name>/Confirm in tasks.md:
- [ ] are now - [x]If not, inform the user and suggest running spec-verify first.
Move the entire spec folder:
.kiro/specs/<feature-name>/ → docs/architecture/specs/<feature-name>/
Create docs/architecture/specs/ if it doesn't exist.
Prepend to the archived proposal.md:
---
archived: YYYY-MM-DD
status: completed
implemented-in: <branch or commit reference>
---
Append to docs/architecture/specs/INDEX.md (create if missing):
| <Feature Name> | YYYY-MM-DD | Completed | Brief description |
.kiro/specs/<feature-name>/ (it now lives in docs)