一键在 Manus 中运行任何 Skill

shape-revision

星标0

分支0

更新时间2026年3月4日 05:40

Shape a spec revision when requirements/responsibilities move. Use this before delta scoping when policy/doctrine requires revision-first flow.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

davidlee

davidlee/im

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

相关职业SOC

基于 SOC 职业分类

项目管理专家商业与金融运营类职业·SOC 13-1082

SKILL.md

readonly

name	shape-revision
description	Shape a spec revision when requirements/responsibilities move. Use this before delta scoping when policy/doctrine requires revision-first flow.

You are establishing the spec-change intent before implementation work.

Inputs:

A change request that moves/rewrites requirements or responsibilities.
Candidate source/destination specs and requirement IDs.

Process:

Read:
- .spec-driver/agents/workflow.md
- .spec-driver/agents/policy.md
- .spec-driver/hooks/doctrine.md
Decide if revision is required:
- If policy/doctrine says revision-first, create/update a revision.
- If the change is implementation-only with no spec movement, stop and use /scope-delta.
Create a revision:
- uv run spec-driver create revision "<summary>" --source SPEC-XXX --destination SPEC-YYY --requirement SPEC-XXX.FR-001
Update the generated RE-XXX.md:
- New/changed requirements (when applicable)
- Requirement moves and rationale
- Lifecycle notes for affected requirements
- Links to related specs/deltas if known
If policy implications appear, stop and /consult.

Outcomes:

A revision exists and captures spec-change intent unambiguously.
Downstream delta/design work can proceed with clear authority.

同仓库更多 Skills

同仓库

boot

davidlee/im

Mandatory onboarding. Every agent MUST execute this on startup, or as soon as becoming aware of it.

2026-03-040

execute-phase

davidlee/im

Execute an active implementation phase against DR/IP intent, keep notes current, and surface blockers early. You MUST use this skill when implementing a delta / IP.

2026-03-040

preflight

davidlee/im

Before starting anything new, understand task, intent, and context.

2026-03-040

doctrine

davidlee/im

Understand project governance to avoid spreading heresy. you

2026-03-040

scope-delta

davidlee/im

Scope intentional change as a delta. Define applies-to specs/requirements, risks, and closure targets before implementation.

2026-03-040

audit-change

davidlee/im

Perform verification/audit pass after implementation (or as discovery/backfill), reconcile against specs/contracts, and route findings into closure or follow-up change.

2026-03-040

name	shape-revision
description	Shape a spec revision when requirements/responsibilities move. Use this before delta scoping when policy/doctrine requires revision-first flow.

You are establishing the spec-change intent before implementation work.

Inputs:

A change request that moves/rewrites requirements or responsibilities.
Candidate source/destination specs and requirement IDs.

Process:

Read:
- .spec-driver/agents/workflow.md
- .spec-driver/agents/policy.md
- .spec-driver/hooks/doctrine.md
Decide if revision is required:
- If policy/doctrine says revision-first, create/update a revision.
- If the change is implementation-only with no spec movement, stop and use /scope-delta.
Create a revision:
- uv run spec-driver create revision "<summary>" --source SPEC-XXX --destination SPEC-YYY --requirement SPEC-XXX.FR-001
Update the generated RE-XXX.md:
- New/changed requirements (when applicable)
- Requirement moves and rationale
- Lifecycle notes for affected requirements
- Links to related specs/deltas if known
If policy implications appear, stop and /consult.

Outcomes:

A revision exists and captures spec-change intent unambiguously.
Downstream delta/design work can proceed with clear authority.