set-a-project-milestone
Set a project milestone with a measurable outcome, acceptance evidence, owner, date, dependencies, and decision consequence. Use when a plan needs a verifiable checkpoint rather than a vague phase label.
소스 정보
- 저장소
- protosphinx/sphinxstack
- 최근 소스 활동
- 2026년 7월 29일 13:55
- 감지된 SKILL.md 언어
- 영어
- 스타
- 3
- 포크
- 0
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- set-a-project-milestone
- category
- start
- description
- Set a project milestone with a measurable outcome, acceptance evidence, owner, date, dependencies, and decision consequence. Use when a plan needs a verifiable checkpoint rather than a vague phase label.
# set-a-project-milestone
A milestone marks a proven state, not elapsed time.
## When to use
- Use for approvals, prototypes, migrations, launches, contracts, readiness, or delivery.
- Do not call a meeting, percentage complete, or task list a milestone without an observable outcome.
## Procedure
1. State the outcome and why it matters to the project decision path.
2. Define in-scope and out-of-scope work, acceptance criteria, and required evidence.
3. Assign accountable owner, target date, approver, contributors, and recipients.
4. Link predecessor and successor dependencies plus lead times.
5. Identify assumptions, risks, resources, and external commitments that can change the date.
6. Define status rules, forecast updates, escalation threshold, and consequence of missing or rejecting the milestone.
7. Obtain owner and approver agreement and add it to the controlled plan.
## Done
- A milestone record documents outcome, scope, criteria, evidence, owner, approver, date, dependencies, and consequence
- Measurability, dependency, ownership, calendar, evidence, escalation, and approval checks verify the checkpoint
GitHub에서 보기