npx claudepluginhub komluk/scaffolding --plugin scaffoldingThis skill uses the workspace's default tool permissions.
Guide for creating `proposal.md` -- the WHY document that anchors the entire workflow.
Integrates Mem0 persistent memory for Claude Code tasks using MCP tools. Retrieves relevant memories on new tasks, stores learnings like decisions and strategies, captures session states.
Creates web-based slidedecks for developers using Slidev with Markdown, Vue components, code highlighting, animations, interactive demos, and presenter notes. Use for technical presentations, conference talks, code walkthroughs, and workshops.
Guide for creating proposal.md -- the WHY document that anchors the entire workflow.
Write to: {specs_path}/proposal.md
Path Enforcement: The specs_path MUST be .scaffolding/conversations/{UUID}/specs/ where {UUID} is a valid UUID (format: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx). NEVER use descriptive folder names.
| Section | Purpose | Content |
|---|---|---|
| Why | Motivation | 1-2 sentences. What problem? Why now? |
| What Changes | Scope | Bullet list. New capabilities, modifications, removals. Mark BREAKING |
| Capabilities | Contract | New + modified capabilities (kebab-case names) |
| Impact | Blast radius | Affected code, APIs, dependencies, systems |
| Agent Assignment | Routing | Table of agents, roles, artifacts |
| Rollback Plan | Safety | Revert points, manual steps, affected systems |
This section creates the contract between proposal and design phases.
user-auth, data-export, api-rate-limiting.scaffolding/openspec/specs/ for existing names## Why
[1-2 sentences: problem + urgency]
## What Changes
- [Specific change 1]
- [Specific change 2]
- **BREAKING**: [Breaking change, if any]
## Capabilities
### New Capabilities
- `capability-name`: Brief description
### Modified Capabilities
- `existing-name`: What requirement is changing
## Impact
[Affected code, APIs, dependencies, systems]
## Agent Assignment
| Agent | Role | Artifacts |
|-------|------|-----------|
| architect | Analyst + Coordinator | proposal.md, design.md, tasks.md |
| researcher | External Research (if needed) | ResearchPack |
| developer | Developer | Source code |
| reviewer | Reviewer | Review report |
## Rollback Plan
- [ ] Identify revert points
- [ ] Document manual rollback steps
- [ ] List affected systems
| Avoid | Instead |
|---|---|
| Vague goals ("improve performance") | Measurable goals ("reduce p95 latency below 200ms") |
| Implementation details | Save for design.md |
| Missing rollback plan | Always include revert strategy |
| Skipping capabilities section | This is the design contract |