Personal plugin marketplace for Claude Code workflow extensions with beads/deciduous tracking integration, lightly and lovingly wrapping ed3d's coding plugins. In desperate search of a name that doesn't suck.
/plugin marketplace add kyle-claude-plugins# Workflow commands (required)
/plugin install workflow-commands@kyle-claude-plugins
# Tracking hooks (optional - session start reminders, git hooks)
chmod +x ~/code/kyle-claude-plugins/plugins/tracking-hooks/hooks/*.sh
chmod +x ~/code/kyle-claude-plugins/plugins/tracking-hooks/hooks/*.py
/plugin install tracking-hooks@kyle-claude-pluginsLocal task/issue tracking stored in .beads/ directory.
# Install
curl -fsSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash
# Verify
bd --versionKey commands:
bd init # Initialize in project
bd create "Task" -t task -p 3 # Create task (priority 0-4)
bd list # List all tasks
bd ready # Show unblocked tasks
bd update <id> --status done # Update status
bd close <id> --reason "Done" # Close taskDecision graph stored in .deciduous/ directory.
# Install
npm install -g deciduous
# Verify
deciduous --versionKey commands:
deciduous init # Initialize in project
deciduous add goal "What I'm doing" -c 80 # Confidence 0-100
deciduous add decision "Choice and why" -c 80
deciduous add action "What I did"
deciduous add outcome "What happened"
deciduous add action "Committed X" --commit HEAD # Link to git
deciduous query # View graphDesign and implementation workflow framework.
# Register marketplace
/plugin marketplace add https://github.com/ed3dai/ed3d-plugins.git
# Install plugins
/plugin install ed3d-plan-and-execute@ed3d-plugins
/plugin install ed3d-research-agents@ed3d-plugins
/plugin install ed3d-basic-agents@ed3d-pluginsIf using --linear flag with /workflow-commands:intake:
- Must have Linear MCP connector enabled in Claude
- Requires access to at least one Linear team
For automatic verification hooks:
pip install pre-commit
pre-commit install # In each projectInitialize beads and deciduous tracking in a project.
/workflow-commands:project-init [--beads-only | --deciduous-only] [--with-guidance]| Flag | Description |
|---|---|
--beads-only |
Only initialize beads, skip deciduous |
--deciduous-only |
Only initialize deciduous, skip beads |
--with-guidance |
Create .ed3d/ directory with customization files |
Creates:
.beads/- Task database.deciduous/- Decision graph.ed3d/- Guidance files (if--with-guidance)
Import features from a roadmap file or inline list.
# From markdown file
/workflow-commands:intake @docs/roadmap.md
# With Linear sync
/workflow-commands:intake @docs/roadmap.md --linear
# Inline features
/workflow-commands:intake "OAuth integration" "Rate limiting" "Audit logging"
# Inline with Linear and team
/workflow-commands:intake "Feature 1" "Feature 2" --linear --team Engineering| Argument | Description |
|---|---|
@file.md |
Path to markdown roadmap file |
"feature" |
Inline feature names (quoted) |
--linear |
Also create Linear issues |
--team <n> |
Linear team name (required if multiple teams) |
Roadmap format:
## Q1 Features
### OAuth Integration
Support Google and GitHub providers.
Priority: High
### Rate Limiting
Token bucket algorithm.
Priority: NormalCreates:
- Beads epic per feature (with priority)
- Linear issue per feature (if
--linear) - Bidirectional links between beads and Linear
Research a topic with automatic tracking.
/workflow-commands:explore <topic> [--codebase-only | --web-only] [--no-tracking]| Flag | Description |
|---|---|
--codebase-only |
Only search local codebase |
--web-only |
Only search web |
--no-tracking |
Skip beads task creation (deciduous still logs) |
Examples:
/workflow-commands:explore OAuth2 PKCE flow
/workflow-commands:explore authentication patterns --codebase-only
/workflow-commands:explore React 19 changes --web-onlyTracking:
- Creates deciduous goal at start
- Creates beads task (unless
--no-tracking) - Logs outcome on completion
- Closes beads task
Start a design plan with decision logging. Wraps ed3d-plan-and-execute:start-design-plan.
/workflow-commands:design [feature description]Tracking:
- Creates beads epic: "Design: <feature>"
- Logs deciduous goal
- Logs every design decision during brainstorming
- Updates beads on completion
Decision logging examples:
deciduous add decision "Chose PostgreSQL over MongoDB because: ACID compliance required, team expertise, JOIN performance" -c 85
deciduous add decision "Using event sourcing pattern because: audit trail required, temporal queries needed" -c 80Create an implementation plan with task creation. Wraps ed3d-plan-and-execute:start-implementation-plan.
/workflow-commands:plan @path/to/design.md <workdir>| Argument | Description |
|---|---|
@design.md |
Path to design document |
workdir |
Working directory (usually .) |
Example:
/clear
/workflow-commands:plan @docs/design-plans/2026-02-10-oauth.md .Tracking:
- Creates beads task per implementation phase
- Sets up task dependencies (sequential)
- Logs planning decisions to deciduous
Execute an implementation plan with status updates. Wraps ed3d-plan-and-execute:execute-implementation-plan.
/workflow-commands:execute <plan-dir> <workdir>| Argument | Description |
|---|---|
plan-dir |
Path to implementation plan directory |
workdir |
Working directory (usually .) |
Example:
/clear
/workflow-commands:execute docs/implementation-plans/2026-02-10-oauth/ .Tracking:
- Updates beads task status per phase (in_progress → done)
- Logs implementation decisions as they happen
- Uses LEARNED pattern for discoveries
Decision logging examples:
deciduous add decision "Implemented retry with exponential backoff because upstream API is flaky" -c 80
deciduous add decision "Resolved circular dependency by extracting shared types to common module" -c 85Final verification with intelligent tooling detection.
/workflow-commands:verify [--skip-tests] [--skip-lint] [--skip-precommit] [--skip-review] [--task <id>]| Flag | Description |
|---|---|
--skip-tests |
Skip test execution |
--skip-lint |
Skip linting |
--skip-precommit |
Skip pre-commit hooks |
--skip-review |
Skip code review |
--task <id> |
Beads task ID to close on success |
Automatic detection:
| Language | Tests | Lint | Format |
|---|---|---|---|
| Python | pytest, tox, nox, unittest | ruff, flake8, pylint | black, ruff format |
| JS/TS | npm test (jest, vitest, mocha) | eslint | prettier |
| Rust | cargo test | cargo clippy | cargo fmt |
| Go | go test | golangci-lint, go vet | gofmt |
Also detects:
- Pre-commit hooks (
.pre-commit-config.yaml) - Type checkers (mypy, tsc)
- Makefile targets
- Package.json scripts
Behavior:
- Detects all project tooling
- Runs tests, linters, formatters, pre-commit
- Attempts auto-fix for formatting issues
- Dispatches code review
- Logs deciduous outcome
- Closes beads task (if
--taskprovided)
Small standalone work that doesn't need design/planning phases.
/workflow-commands:task "<task description>" [--priority <0-4>]| Argument | Description |
|---|---|
"<description>" |
Task description (quoted) |
--priority |
0=Critical, 1=High, 2=Medium, 3=Normal (default), 4=Backlog |
Use when: Work is clear, takes <1 hour, doesn't require architectural decisions.
Examples:
/workflow-commands:task "Add logging to auth middleware"
/workflow-commands:task "Update error message for invalid email" --priority 2Fix a bug with investigation and root cause tracking.
/workflow-commands:bug "<bug description>" [--priority <0-4>] [--blocks <task-id>]| Argument | Description |
|---|---|
"<description>" |
Bug description (quoted) |
--priority |
0=Critical, 1=High, 2=Medium (default), 3=Normal, 4=Backlog |
--blocks |
Link to task this bug is blocking |
Workflow:
- Creates beads bug
- Investigate → find root cause
- Fix → verify
- Close bug
Examples:
/workflow-commands:bug "Login button doesn't respond on mobile"
/workflow-commands:bug "Users can't checkout" --priority 1
/workflow-commands:bug "Auth crashes on empty token" --blocks beads-a1b2Resume work on an existing beads task.
/workflow-commands:continue [<task-id>]| Argument | Description |
|---|---|
<task-id> |
Beads task ID (e.g., beads-a1b2 or just a1b2) |
If no task ID: Shows available tasks (bd ready, bd list --status=in_progress).
Examples:
/workflow-commands:continue beads-a1b2 # Resume specific task
/workflow-commands:continue # Show available tasks| Start From | When to Use | Creates |
|---|---|---|
/workflow-commands:design |
New feature needing architecture | Epic |
/workflow-commands:plan |
Have design doc, need tasks | Phase tasks |
/workflow-commands:task |
Small standalone work (<1hr) | Single task |
/workflow-commands:bug |
Fix a bug | Bug |
/workflow-commands:continue |
Resume existing work | Nothing (uses existing) |
/workflow-commands:explore |
Research before design | Research task |
/workflow-commands:intake |
Import roadmap | Epics |
/workflow-commands:project-init # Once per project
│
▼
/workflow-commands:intake @roadmap.md --linear # Import features
│
│ ┌───────────────────────────────────────┐
│ │ For each feature: │
▼ ▼ │
/workflow-commands:explore <topic> │ ← deciduous: goal/outcome
│ │ beads: research task
▼ │
/workflow-commands:design │ ← deciduous: ALL design decisions
│ │ beads: design epic
▼ │
/clear │
/workflow-commands:plan @design.md . │ ← deciduous: planning decisions
│ │ beads: phase tasks
▼ │
/clear │
/workflow-commands:execute <plan-dir> . │ ← deciduous: impl decisions
│ │ beads: status updates
▼ │
/workflow-commands:verify --task <epic-id> │ ← deciduous: outcome
│ │ beads: close epic
▼ │
git commit / PR ────────────────────────────────┘
For smaller tasks that don't need full design:
/workflow-commands:task "Add logging to auth middleware"
# ... work directly ...
/workflow-commands:verify
git commit -m "feat: add auth middleware logging"/workflow-commands:bug "Users can't login on mobile"
# ... investigate root cause ...
# ... fix it ...
/workflow-commands:verify
git commit -m "fix: mobile login issue"/workflow-commands:continue beads-a1b2 # Resume specific task
# or
/workflow-commands:continue # Show available tasksRun /workflow-commands:project-init --with-guidance to create:
.ed3d/
├── design-plan-guidance.md # Customize design phase
└── implementation-plan-guidance.md # Customize implementation
# Design Plan Guidance
## Domain Context
<!-- Describe your project's domain, terminology, key concepts -->
## Architectural Constraints
<!-- Decisions that designs must follow -->
- All services must be stateless
- Use PostgreSQL for persistence
- REST APIs only (no GraphQL)
## Technology Stack
### Required
- Python 3.11+
- FastAPI
- PostgreSQL
### Preferred
- Redis for caching
- Celery for async tasks
### Forbidden
- MongoDB (we standardized on PostgreSQL)
- Synchronous external API calls in request handlers
## Stakeholders
<!-- Who approves designs? -->
## Design Conventions
<!-- Project-specific patterns --># Implementation Plan Guidance
## Coding Standards
<!-- Reference style guide or key conventions -->
- Follow PEP 8
- Use type hints everywhere
- Docstrings for public functions
## Testing Requirements
- Minimum 80% coverage for new code
- Integration tests for API endpoints
- Unit tests for business logic
## Review Criteria
- Security review for auth changes
- Performance review for database changes
## Quality Gates
- All tests pass
- No new lint errors
- Type check passes (mypy)
- Pre-commit hooks pass
## Build & Deploy
- CI runs on push to main
- Deploy via GitHub ActionsThe verify skill auto-detects tooling, but you can influence it by:
-
Adding config files - The skill looks for:
pytest.ini,pyproject.toml(pytest)ruff.toml,.ruff.toml(ruff).pre-commit-config.yaml(pre-commit)- etc.
-
Package.json scripts - Define
test,lintscripts:{ "scripts": { "test": "vitest run", "lint": "eslint . && prettier --check ." } } -
Makefile targets - The skill checks for:
test: pytest -v lint: ruff check . && mypy . verify: test lint pre-commit run --all-files
The workflow commands explicitly log decisions. For best results:
Always include:
- What was decided
- What alternatives were considered
- Why this choice was made
- Confidence level (50 = tentative, 90 = very confident, scale 0-100)
Good example:
deciduous add decision "Chose Redis for session storage because: 1) sub-ms latency required, 2) built-in TTL for session expiry, 3) team already has Redis expertise. Considered: PostgreSQL (too slow), Memcached (no persistence)." -c 85Bad example:
deciduous add decision "Using Redis" -c 80kyle-claude-plugins/
├── .claude-plugin/
│ └── marketplace.json
├── plugins/
│ ├── workflow-commands/
│ │ ├── .claude-plugin/plugin.json
│ │ ├── commands/
│ │ │ ├── project-init.md
│ │ │ ├── intake.md
│ │ │ ├── explore.md
│ │ │ ├── design.md
│ │ │ ├── plan.md
│ │ │ ├── execute.md
│ │ │ ├── verify.md
│ │ │ ├── task.md # NEW
│ │ │ ├── bug.md # NEW
│ │ │ └── continue.md # NEW
│ │ └── skills/
│ │ ├── project-init/SKILL.md
│ │ ├── intake/SKILL.md
│ │ ├── exploring/SKILL.md
│ │ ├── designing/SKILL.md
│ │ ├── planning/SKILL.md
│ │ ├── executing/SKILL.md
│ │ ├── verifying/SKILL.md
│ │ ├── task/SKILL.md # NEW
│ │ ├── bug/SKILL.md # NEW
│ │ ├── continue/SKILL.md # NEW
│ │ └── beads-deciduous-integration/SKILL.md
│ └── tracking-hooks/
│ ├── .claude-plugin/plugin.json
│ └── hooks/
│ ├── hooks.json
│ ├── session-start-tracking.sh
│ └── git-beads-reminder.py
└── README.md
MIT