본문으로 건너뛰기
cccskills
무료GitHub에 공개

sr:save

Phase 9 of the SRS workflow. Saves all project context to _context/ files so future Claude sessions can resume without re-reading the full SRS.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md5.1 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

sr:save

Goal: distil the entire project into compact, re-loadable context files. A future session should be able to load just _context/ and have full project understanding.


Step 0 — Identify Project

AskUserQuestion: "Which project to save context for? (slug)"

Read all available files in projects/{slug}/. Run python .claude/scripts/srs_validator.py --dir projects/{slug}/srs/ --stats and use its counts for quality_standards.md / session-notes.md below instead of recounting by hand.


Step 1 — Write Context Files

Write all files under projects/{slug}/_context/:

vision.md

# Vision — {Project Name}

## Problem Statement
{what problem does this system solve? 2–3 sentences from spec §1}

## Solution Summary
{what the system does, for whom, and the core value proposition}

## Success Metrics
{how we measure success — from spec §1 or brainstorm}

## Constraints
{top 3 hard constraints — tech, timeline, compliance}

features.md

# Features — {Project Name}

## IN Scope (v1.0)
| Feature | Priority | Key FRs | Notes |
|---------|----------|---------|-------|
{every confirmed in-scope feature, one row each}

## OUT of Scope (v1.0 — Deferred)
| Feature | Reason | Target version |
|---------|--------|---------------|
{every explicitly excluded feature}

tech_stack.md

# Tech Stack — {Project Name}

## Confirmed Stack
| Layer | Technology | Constraint type |
|-------|-----------|----------------|
{language, framework, DB, cloud, CI/CD — from spec §5}

## Integration Points
| System | Protocol | Direction | Auth |
|--------|----------|-----------|------|
{every external system — from SRS §3.1.3}

## Compliance Requirements
{applicable regulations + specific technical obligations}

glossary.md

# Glossary — {Project Name}

Copy of Appendix A from the SRS. Every term, acronym, abbreviation.
Include: domain terms | project-specific terms | role names | system names

quality_standards.md

# Quality Standards — {Project Name}

## Confirmed NFR Targets
| ID | Characteristic | Target | Status |
|----|---------------|--------|--------|
{all NFRs from SRS §3.3 — confirmed targets and [TBD] items}

## Validation Status
Validator verdict: {COMPLIANT | PARTIALLY COMPLIANT | NON-COMPLIANT}
Open warnings: {count}

session-notes.md

# Session Notes — {Project Name}

## Key Decisions Made
{numbered list — every explicit scope, tech, or design decision from brainstorm}

## Assumptions
{numbered list — from spec §8, with invalidation risk level}

## Open Items
{all [TBD] items — copied from appendix-b-open-issues.md}

## Next Steps
1. Resolve open items in appendix-b (see quality_standards.md for owners)
2. Dev team walkthrough of SRS §3.2 (functional requirements)
3. QA team review of GWT acceptance criteria
4. Architecture review of NFR targets before sprint planning

## SRS Location
projects/{slug}/srs/ — {N} section files
Master index: projects/{slug}/srs/00-master-index.md

Step 2 — Final Summary

Output the complete workflow completion summary:

╔══════════════════════════════════════════════════╗
║           SRS Workflow Complete                  ║
╠══════════════════════════════════════════════════╣
║ Project:     {name}                              ║
║ Slug:        {slug}                              ║
║ Location:    projects/{slug}/                    ║
╠══════════════════════════════════════════════════╣
║ Brainstorm:  projects/{slug}/brainstorm.md       ║
║ Spec:        projects/{slug}/spec.md             ║
║ Plan:        projects/{slug}/plan/ (12 files)    ║
║ SRS:         projects/{slug}/srs/  (11 files)    ║
║ Improvement: projects/{slug}/improvement-report.md ║
║ Context:     projects/{slug}/_context/ (6 files) ║
╠══════════════════════════════════════════════════╣
║ FRs:         {total} ({E} Essential / {C} Cond / {O} Opt) ║
║ NFRs:        {total} ({confirmed} confirmed / {TBD} TBD)  ║
║ Verdict:     {COMPLIANT | PARTIALLY COMPLIANT}   ║
║ Open items:  {count}                             ║
╚══════════════════════════════════════════════════╝

Share with your team:
  SRS  → projects/{slug}/srs/00-master-index.md
  Risks→ projects/{slug}/improvement-report.md

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Build robust backend systems — APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), databases, performance optimization, security (OWASP Top 10), scalability patterns (microservices, caching, sharding), and testing. Use when designing APIs, implementing auth, optimizing queries, handling security vulnerabilities, building microservices, or developing production-ready backend systems.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

caveman

무료

Terse output mode — strips filler/articles/hedging, ~75% token reduction. Activate whenever: context is filling up, user says be brief/terse/caveman/less tokens, or CAVEMAN_TRIGGERED appears in context. Persists every response until CAVEMAN_RELEASED or user says stop/normal mode.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

Explore and debate solutions before writing code. Use when the user poses a design question, asks "how should I approach X", wants to think through options before committing, or says anything like "let's brainstorm", "what's the best way to...", "I'm not sure how to tackle this", or "should I use X or Y". Always runs before /ck:plan for novel or ambiguous features. No code is written — only: explore → clarify → spec → report.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

ck-cook

무료

Implement a feature phase by phase from a phased JSON master or Markdown plan. Before each phase, confirm whether to create/run unit tests and whether to run ck:quality, unless explicit flags supply those choices. Supports token-budgeted execution, resumable state, and TDD handoff to ck:test.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

ck-fix

무료

Fix a bug using Scout → Diagnose → Fix → Review → Finalize. Use when the user pastes an error message, stack trace, or test failure, or says "fix this bug", "something's broken", "tests are failing", "I'm getting an error". Also accepts `--from-quality <report>` or `--from-test <report>` to fix exactly the findings/failures a report lists. Modes (pick one): --fast (trivial errors — lint, type, build — skip scout and review), --hard (mandatory review, no auto-approve).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

ck-plan

무료

Plan a feature or system before implementation. Use when the user says "plan this", "I want to build X", "how do I implement Y", or when /ck:brainstorm produces a spec.md. Always run before /ck:cook. Modes (pick one): --fast (simple, single-file), --hard (research + red-team + validate). Composable flag (combine with any mode): --tdd — propagates into the cook pipeline. Every phase gets Design Constraints and Quality/Testing State; ck:cook confirms optional test and quality checks per phase.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

DangQuangSE/team-development-skills192026년 10월 19일 업데이트

DangQuangSE의 스킬 모두 보기

이 스킬의 문제 신고