AgentSkillsCN

klondike-agent-workflow

使用klondike CLI管理多会话AI代理的工作流。适用于klondike管理的项目（即包含.klondike/目录的项目），在开启或结束编码会话、追踪功能的生命周期，或在上下文窗口重置时保持一致性时，可使用此技能。触发时机包括会话管理、功能追踪、进度交接，以及验证工作流。

SKILL.md
--- frontmatter
name: klondike-agent-workflow
description: Manage multi-session AI agent workflows using klondike CLI. Use when working on klondike-managed projects (those with .klondike/ directory), when starting/ending coding sessions, tracking features through lifecycle, or maintaining coherence across context window resets. Triggers on session management, feature tracking, progress handoffs, and verification workflows.

Klondike Agent Workflow

Klondike bridges context windows for long-running agent sessions. Critical: Always use CLI commands—never directly read/edit .klondike/*.json files or agent-progress.md.

CRITICAL: Common Mistakes to Avoid

❌ NEVER do these:

  • •klondike --help (wrong syntax - use klondike alone or klondike <command> without --help)
  • •klondike feature --help (wrong - just run the command, it will show usage)
  • •Read .klondike/features.json directly (use klondike feature list)
  • •Edit agent-progress.md manually (auto-generated, changes are lost)
  • •klondike feature start without feature ID (must be klondike feature start F001)
  • •Feature IDs like f001 or 1 (must be uppercase: F001)

✓ DO these:

  • •klondike alone shows all commands
  • •klondike feature list to see features
  • •klondike feature show F001 for details
  • •klondike status to see project overview

Quick Decision Tree

code
Starting work?     → klondike status → klondike session start --focus "F001 - desc"
Working on feature → klondike feature start F001
Feature complete?  → Test E2E → klondike feature verify F001 --evidence "..."
Blocked?           → klondike feature block F001 --reason "..."
Ending session?    → klondike session end --summary "..." --next "..."

Session Lifecycle

1. Session Start (Always Do First!)

bash
klondike status                                    # See project state
klondike validate                                  # Check artifact integrity
klondike session start --focus "F001 - Login UI"  # Begin session
klondike feature start F001                        # Mark feature in-progress

2. During Work

  • •One feature at a time (tracked by feature start)
  • •Commit after each meaningful change
  • •Test incrementally, not at end
  • •If blocked: klondike feature block F001 --reason "..."

3. Session End (Before Leaving!)

bash
klondike feature verify F001 --evidence "test-results/F001.png"
klondike session end --summary "Done" --next "Implement logout"

Core Commands

ActionCommandNotes
Statusklondike statusAlways start here
Add featureklondike feature add "desc" --notes "hints"--notes is critical
Start featureklondike feature start F001One at a time
List featuresklondike feature listNever read JSON directly
Show detailsklondike feature show F001View single feature
Verifyklondike feature verify F001 --evidence "proof"E2E test first
Blockklondike feature block F001 --reason "why"When stuck
Start sessionklondike session start --focus "F001 - desc"Begin work
End sessionklondike session end --summary "..." --next "..."Before leaving

Essential Rules

Always:

  • •Start every session with klondike status to see project state
  • •Use --notes when adding features (gives future agents critical context)
  • •Capture evidence (screenshots, logs) before feature verify
  • •Run pre-commit checks before every commit
  • •End sessions with session end --summary ... --next ...

Never:

  • •Use klondike --help or klondike feature --help (wrong syntax - see Common Mistakes)
  • •Read or edit .klondike/*.json files directly (use CLI commands)
  • •Edit agent-progress.md manually (auto-generated, edits are lost)
  • •Verify features without E2E testing (unit tests aren't enough)
  • •Commit code with failing tests, lint errors, or build failures

Pre-Commit Checks

Detect project type and run checks. Never commit if any fail.

Python (uv): uv run ruff check src tests && uv run pytest
Node.js: npm run lint && npm run build && CI=true npm test
Rust: cargo clippy && cargo test
Go: golangci-lint run && go test ./...

Reference Files (Load As Needed)

Load these only when you need specific details: