菜单
Create a drift log (DRL) documenting an incident, unexpected finding, or post-mortem. Register it in INDEX.md and cross-reference affected modules.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Write a new Architecture Decision Record (ADR) using the project's numbering convention. Register it in INDEX.md and cross-reference affected module plans.
Add admin dashboard CRUD (list/detail/new/edit/delete) for a new entity following the Jobs and About patterns. Covers migration, DB helpers, React components, and API endpoints.
Create a numbered SQLite migration file and wire it into the MIGRATIONS array in db.rs. Follows the NNN_description.sql naming convention.
Create a new plan module file following CONVENTIONS.md template, register the domain code, and update INDEX.md. Keeps the plan system as the single source of truth.
Add a new Axum JSON API endpoint and/or React page route following the services/ui + web/ SPA patterns. Handles handler creation, router registration, and React component wiring.
Add a new AWS Secrets Manager secret following the W-SEC policy. Covers xtask registration, infra HCL, IAM policy, Lambda env wiring, and the put command.
| name | add-drift-log |
| description | Create a drift log (DRL) documenting an incident, unexpected finding, or post-mortem. Register it in INDEX.md and cross-reference affected modules. |
| argument-hint | [topic] |
Document an incident, gap, or unexpected deviation from the plan. Drift logs (DRLs) are the project's post-mortem / lessons-learned format.
Path: plans/drift/DRL-<YYYY-MM-DD>-<topic>.md
YYYY-MM-DD formatopentofu-migration, function-url-auth, contact-form)plans/drift/DRL-2026-04-07-email-lambda-timeout.mdTemplate:
# DRL-<YYYY-MM-DD>-<topic>
**Date:** YYYY-MM-DD
**Severity:** low | medium | high
**Affected modules:** W-XXX, W-YYY
## Summary
One paragraph describing what happened.
## Entries
| ID | Finding | Status | Resolution |
|----|---------|--------|-----------|
| DRL-<TOPIC>-1 | Description of the gap/issue | RESOLVED / OPEN | What was done or needs doing |
## Lessons Learned
- Bullet points of what to do differently
## Cross-References
- → W-XXX (affected module plan)
- → ADR-NNN (if an ADR was created or changed as a result)
File: plans/INDEX.md → "Drift Log Index" table
Add a new row:
| DRL-<YYYY-MM-DD>-<topic> | <YYYY-MM-DD> | <Human readable topic> | <N> entries |
For each affected module plan (e.g. plans/modules/opentofu.md):
W-XXX.6 Cross-References, add:
→ DRL-<YYYY-MM-DD>-<topic>
If the drift log surfaces new work:
W-XXX.4.N items to the affected module fileplans/INDEX.md priority queue under appropriate P-level| File | Date | Topic |
|---|---|---|
| DRL-2026-03-18-terraform | 2026-03-18 | Terraform first-run gaps |
| DRL-2026-03-18-xtask | 2026-03-18 | xtask/justfile gaps |
| DRL-2026-03-25-opentofu | 2026-03-25 | OpenTofu migration audit |
| DRL-2026-03-27-function-url-auth | 2026-03-27 | Lambda Function URL auth incident |
| DRL-2026-04-03-contact-form | 2026-04-03 | Contact Form + SES implementation |
| DRL-2026-04-03-pow-apigateway | 2026-04-03 | POST+PoW via API Gateway |
plans/drift/ — all drift log filesplans/INDEX.md — drift log index tableplans/CONVENTIONS.md — DRL naming rules