mirror of
https://github.com/alibaba/higress.git
synced 2026-07-23 12:50:34 +08:00
d5f2b624fb
Signed-off-by: johnlanni <johnlanni@users.noreply.github.com> Co-authored-by: johnlanni <johnlanni@users.noreply.github.com> Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
25 lines
928 B
Markdown
25 lines
928 B
Markdown
---
|
|
name: issue-spec-archive
|
|
description: Create the post-merge durable spec archive PR for an issue-spec change.
|
|
license: MIT
|
|
compatibility: Requires issue-spec CLI.
|
|
metadata:
|
|
author: issue-spec
|
|
version: "1.0"
|
|
generatedBy: "issue-spec"
|
|
---
|
|
|
|
# Issue Spec Archive
|
|
|
|
Use when the user asks for /issue-spec:archive, issue-spec archive, or creating the post-merge durable spec PR.
|
|
|
|
## Steps
|
|
|
|
1. Confirm the implementation PR is merged.
|
|
2. Create the durable spec PR:
|
|
|
|
issue-spec archive durable-spec --repo higress-group/higress --proposal <issue> --capability <capability> --create-pr --branch issue-spec/durable-spec-<capability> --json
|
|
|
|
3. Review the durable spec PR for long-lived behavior only. Do not copy process records, review findings, or verification logs into durable specs.
|
|
4. After durable spec PR merge, keep proposal/design/implement issues as audit history unless the project policy says to close them.
|