skill create-adr

This commit is contained in:
2026-04-29 00:38:11 +07:00
parent c616fcf037
commit fac874e747
4 changed files with 96 additions and 2 deletions
+3 -2
View File
@@ -35,6 +35,7 @@ description: Phase 2 skill. Use when issue scope is locked by Product Owner (Pha
- List files to change.
- State whether `README.md` or `.env.example` must change.
- State whether an ADR is required or not required.
- If ADR is required or recommended, invoke `create-adr` before finalizing the implementation summary and PR body.
- Flag risks or tradeoffs.
- Post plan as comment: `mcp__gitea__.issue_write` (`method: "add_comment"`).
- **Wait for "Approved" before coding.** Stop here.
@@ -51,7 +52,7 @@ description: Phase 2 skill. Use when issue scope is locked by Product Owner (Pha
```
- Implement following the plan (surgical changes only).
- Update `README.md` and `.env.example` when config, endpoint, or runtime behavior changes.
- If the change introduces a durable behavior, contract, architecture, or workflow decision, create/update `docs/adr/**`.
- If the change introduces a durable behavior, contract, architecture, or workflow decision, use `create-adr` and create/update `docs/adr/**`.
- Run validation:
```
gofmt -l .
@@ -96,7 +97,7 @@ description: Phase 2 skill. Use when issue scope is locked by Product Owner (Pha
- Missing required tests, docs, `.env.example` updates, or ADRs is a quality failure unless explicitly justified in both the issue comment and PR body.
- Never claim completion without fresh verification output.
- Keep changes strictly scoped to the approved plan.
- If the change needs durable documentation, create/update `docs/adr/**`. Do not commit `docs/superpowers/**` planning artifacts.
- If the change needs durable documentation, use `create-adr` and create/update `docs/adr/**`. Do not commit `docs/superpowers/**` planning artifacts.
## Next skill
After PR is created, the user invokes `/review-pr <pr-number>` on the Reviewer agent.