Implement the plan from a spec change
Archive a completed spec change
Document the system in its current state — domain, architecture, and all relevant perspectives.
Enter explore mode - think through ideas, investigate problems, clarify requirements. Use when the user wants to think through an idea, compare approaches, or understand a problem before proposing changes.
Review spec artifacts, apply user annotations, and produce a clean consolidated version
Personal marketplace for Claude Code plugins.
Open Claude Code in any project directory:
/plugin marketplace add tgartner/till-claude-code-marketplace
(Recommended)/plugin marketplace add .//plugin install spec@till-claude-code-marketplace
Select "Install for all collaborators on this repository (project scope)" or "Install for just me (user scope)" as needed. Restart Claude Code to load new plugins.
| Plugin | Description | Commands |
|---|---|---|
| spec | Spec-driven change management workflow | /spec:overview, /spec:document-system, /spec:explore, /spec:propose, /spec:iterate, /spec:apply, /spec:archive |
Normally, installing a plugin copies its files into Claude Code's internal storage. That means every edit requires a reinstall — slow for active development.
Use --plugin-dir to bypass this: it loads the plugin straight from your local
files so changes take effect immediately.
# Launch Claude Code with the plugin loaded from source
claude --plugin-dir ./plugins/spec
Then iterate without restarting:
/reload-pluginsCommit and push only when the plugin is stable, then install it from the marketplace as usual.
| Approach | How | Tradeoff |
|---|---|---|
--plugin-dir | claude --plugin-dir ./plugins/x | Recommended. Live reload, but you must pass the flag at every startup |
| Local marketplace | /plugin marketplace add ./ then /plugin install x | One-time setup, but files are copied — must reinstall after changes |
| Symlinks | ln -s /path/to/repo/plugins/x ~/.claude/plugins/x | Changes reflected live, but manual setup and fragile |
Globally installed plugins can be disabled for a specific project via
.claude/settings.json (git-committed, team-wide) or
.claude/settings.local.json (local only, not committed):
{
"enabledPlugins": {
"spec@till-claude-code-marketplace": false
}
}
Alternatively, uninstall a plugin only for the current project:
/plugin uninstall spec@till-claude-code-marketplace --scope project
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
npx claudepluginhub tillg/till-claude-code-marketplace --plugin specConvert Markdown files to beautifully formatted PDFs with tables, code blocks, mermaid diagrams, images, and ASCII art
Spec-driven development workflow system with structured phases: Requirements → Design → Tasks → Implementation
Autonomous spec-driven development workflow with multi-agent collaboration, specification management, and task orchestration
Specification-Driven Development with Process Discipline for Claude Code
Skills-first specification-driven development framework with 7 agent skills for planning, implementation, review, and shipping. Natural language activation with intelligent agent orchestration. Includes /plan, /implement, /research commands plus managing-specifications, implementing-features, and reviewing-and-shipping skills.
Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses