Help us improve
Share bugs, ideas, or general feedback.
npx claudepluginhub jvishnefske/swiss-cheese --plugin swiss-cheeseHow this command is triggered — by the user, by Claude, or both
Slash command
/swiss-cheese:designThe summary Claude sees in its command listing — used to decide when to auto-load this command
You are conducting requirements analysis to produce a task specification.
## Goal
Produce `docs/plans/tasks.toml` - a validated task list ready for implementation.
## Process
{{#if requirements_source}}
1. Read and analyze: `{{requirements_source}}`
{{else}}
1. Look for existing requirements in: README.md, docs/, requirements.md, design.md
{{/if}}
2. Extract functional requirements with testable acceptance criteria
3. Break into implementable tasks with dependencies
4. Validate the task graph (no cycles, all deps exist)
5. Write `docs/plans/tasks.toml`
## Task Specification Schema (TOM.../designDesigns system architecture, APIs, components, and databases producing specifications, diagrams, or code. Accepts target and optional --type (architecture|api|component|database) and --format flags.
/designGuides interactive frontend design workflow: project discovery, trend research, moodboard creation, color/typography selection, and production-ready code generation.
/designCreates comprehensive feature design documents with research and architecture for a given feature name or idea.
/designGenerates Markdown technical design document framework for a feature (doc mode, default). Also supports checklist mode for S-Tier SaaS design quality checks.
/designEnforces SwiftUI design rules for uniform constants, flexible accessible layouts, system styling, and inclusive practices across devices.
/designDesigns system architecture with mandatory C4 (Mermaid) diagrams and tech stack recommendations, consulting prior requirements and flagging contradictions.
Share bugs, ideas, or general feedback.
You are conducting requirements analysis to produce a task specification.
Produce docs/plans/tasks.toml - a validated task list ready for implementation.
{{#if requirements_source}}
{{requirements_source}}
{{else}}docs/plans/tasks.tomlversion = 1
status = "ready_for_implementation" # or: "draft", "needs_review"
[project]
name = "project-name"
description = "Brief project description"
[[tasks]]
id = "task-001"
title = "Short imperative title"
acceptance = "Specific testable criteria"
deps = [] # List of task IDs this depends on
status = "pending" # pending | in_progress | complete
spec_file = "specs/task-001.md" # Optional: detailed specification
[[tasks]]
id = "task-002"
title = "Another task"
acceptance = "Tests pass, no compiler warnings"
deps = ["task-001"] # Depends on task-001
status = "pending"
pendingBefore setting status = "ready_for_implementation":
Create docs/plans/tasks.toml with:
ready_for_implementationEnsure a Makefile exists with verification target:
.PHONY: verify
verify:
cargo build --all-targets 2>&1 | grep -E "^warning:" && exit 1 || true
cargo test --all-features
cargo clippy --all-targets -- -D warnings
cargo fmt --check
The Stop hook runs make verify before allowing completion.
After completing the design:
/swiss-cheese:implementation to begin TDD workflow