사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/filipgutica/filip-stack --skill checkpoint시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Checkpoint
Use only when explicitly invoked. Capture the requested scope in conversation unless the user requests a saved file.
Establish the current state
Identify the outcome and sources. Inspect each repository's identity, branch, HEAD, dirty state, and relevant files. For other work, identify the authoritative document or tracker and observed state.
Reconcile conversation claims with current evidence. Distinguish intended, attempted, implemented, and verified outcomes. Plans and agent claims do not prove completion.
Include only material decisions, completed outcomes, outstanding work, blockers, verification, and the next action. Preserve unrelated dirty changes.
Verification evidence
Identify each check's command, result, and covered revision or working-tree state. Use available results or saved evidence; do not rerun expensive checks solely for a checkpoint.
Flag results invalidated by later relevant changes. When the tested state is unknown, label results historical and current verification unknown. List unconfirmed or unrun required checks; never report unavailable evidence as passed.
Output
Use this shape, omitting empty optional sections:
# Checkpoint: <subject>
Date: <timestamp with timezone>
## Source
<Work item or document; repository, branch, revision, and relevant dirty state>
## Completed
<Confirmed outcomes with bounded evidence; distinguish implemented from verified>
## Remaining
<Outstanding work>
## Blockers and decisions
<Material blockers, unresolved decisions, and settled decisions needed to resume>
## Verification
<Checks, results, covered state, and what remains unverified>
## Next action
<Concrete starting point for continuation>Save only when requested
Honor a supplied destination. Otherwise save a new snapshot at:
~/.engineering-workflow/<project-or-subject>/checkpoints/YYYY-MM-DD-HHMM-<subject>.mdUse descriptive names. Preserve earlier snapshots; add a suffix on filename collision. Create only the checkpoint and parent directory, with no registry, task ledger, companion artifact, or automatic updates.
Check that every completion and verification claim has evidence or an explicit uncertainty label. Return the saved path when applicable.
On resume, treat the checkpoint as historical: recheck current sources and repository state before acting. This skill is read-only except for an explicitly requested checkpoint file. It does not authorize code changes, tracker updates, commits, or publication.