원클릭으로 Manus에서 모든 스킬 실행

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 저장소 열기 Creator 저장소 보기

다운로드

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.