thuanle/claw-email

Fork 0

Files

T

thuanleandClaude Opus 4.7 b013c68988

CI / fmt (pull_request) Successful in 4m56s

Details

CI / test (pull_request) Successful in 10m49s

Details

docs: add ADR workflow and update skills

- Add docs/adr/README.md with ADR format, rules, and index
- Add ADR-0001: IMAP thread resolution via In-Reply-To + References
- Add Documentation Rules section to AGENT.md
- Update validate-issue skill: flag ADR-requiring changes
- Rename do-task → implement-task for clearer semantics
- Update review-pr skill: accept docs/adr/, reject agent artifacts

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

2026-04-28 05:47:37 +07:00

1.9 KiB

Raw Blame History

name, description

name	description
validate-issue	Phase 1 skill. Use when a Gitea issue is created or updated and needs requirement validation. Analyze, clarify, and lock scope as Product Owner. Do NOT implement.

Validate Issue

Phase: 1 — Requirement Refinement Role: Product Owner

When to invoke

User says: "check issue #X", "validate issue #X", "/validate-issue #X"
A new issue is created or an existing issue is updated with new information.

Prerequisite

Issue exists on Gitea.

Workflow

Load issue
- Read issue: mcp__gitea__.issue_read (method: "get").
- Read comments: mcp__gitea__.issue_read (method: "get_comments").
Analyze
- Is the problem statement clear?
- Is the scope well-defined or too broad?
- Is it technically feasible?
- If needed, read relevant code: mcp__gitea__.get_file_contents.
Decide
- Unclear or incomplete:
  - Post clarifying questions: mcp__gitea__.issue_write (method: "add_comment").
  - Stop. Wait for user to respond, then re-run this skill.
- Clear and feasible:
  - Post Final Requirements (see format below).
  - If the change likely needs a durable ADR, add a note: "ADR recommended: this change locks in a behavior/contract that future work must preserve."
  - This locks the scope and signals Phase 2 can begin.

Final Requirements format

## Final Requirements

**Summary:** <one-line summary>

**Scope:**
- <requirement 1>
- <requirement 2>

**Out of scope:**
- <explicitly excluded items>

**Acceptance criteria:**
- <verifiable check 1>
- <verifiable check 2>

Rules

Use Gitea MCP tools for all operations.
Do NOT write code, create branches, or create PRs.
Do NOT proceed to Phase 2 — that is a separate skill.

Next skill

After Final Requirements are posted, the user invokes /do-task <issue-id> on the Developer agent.

1.9 KiB Raw Blame History