Creates comprehensive implementation plans with exact file paths, complete code examples, and verification steps for engineers with zero codebase context.
/plugin marketplace add lerianstudio/ring/plugin install ring-default@ringThis skill inherits all available tools. When active, it can use any tool Claude has access to.
This skill dispatches a specialized agent to write comprehensive implementation plans for engineers with zero codebase context.
Announce at start: "I'm using the writing-plans skill to create the implementation plan."
Context: This should be run in a dedicated worktree (created by brainstorming skill).
Step 1: Query Historical Precedent (MANDATORY)
Before planning, query the artifact index for historical context:
# Keywords MUST be alphanumeric with spaces only (sanitize before use)
python3 default/lib/artifact-index/artifact_query.py --mode planning "keywords" --json
Keyword Extraction (MANDATORY):
Safety: Never include shell metacharacters (;, $, `, |, &) in keywords.
Results inform the plan:
successful_handoffs → Reference patterns that workedfailed_handoffs → WARN in plan, design to avoidrelevant_plans → Review for approach ideasIf is_empty_index: true → Proceed without precedent (normal for new projects).
Step 2: Dispatch Write-Plan Agent
Dispatch via Task(subagent_type: "write-plan", model: "opus") with:
docs/plans/YYYY-MM-DD-<feature-name>.mdStep 3: Validate Plan Against Failure Patterns
After the plan is saved, validate it against known failures:
python3 default/lib/validate-plan-precedent.py docs/plans/YYYY-MM-DD-<feature>.md
Interpretation:
PASS → Plan is safe to executeWARNING → Plan has >30% keyword overlap with past failures
Note: If artifact index is unavailable, validation passes automatically (nothing to check against).
Step 4: Ask User About Execution
Ask via AskUserQuestion: "Execute now?" Options:
subagent-driven-developmentexecuting-plansContext preservation (reading many files keeps supervisor clean) | Model power (Opus for comprehensive planning) | Separation of concerns (supervisor orchestrates, agent plans)
Query precedent → Explore codebase → identify files → break into bite-sized tasks (2-5 min) → write complete code → include exact commands → add review checkpoints → include Historical Precedent section → verify Zero-Context Test → save to docs/plans/YYYY-MM-DD-<feature>.md → report back
Every plan: Historical Precedent section | Header (goal, architecture, tech stack) | Verification commands with expected output | Exact file paths (never "somewhere in src") | Complete code (never "add validation here") | Bite-sized steps with verification | Failure recovery | Review checkpoints | Zero-Context Test | Recommended agents per task | Avoids known failure patterns
| Task Type | Agent |
|---|---|
| Backend API/services | backend-engineer-{golang,typescript} |
| Frontend/BFF | frontend-bff-engineer-typescript |
| Infra/CI/CD | devops-engineer |
| Testing | qa-analyst |
| Reliability | sre |
| Fallback | general-purpose (built-in, no prefix) |
| Option | Description |
|---|---|
| Execute now | Fresh subagent per task, code review between tasks → subagent-driven-development |
| Parallel session | User opens new session, batch execution with human review → executing-plans |
| Save for later | Plan at docs/plans/YYYY-MM-DD-<feature>.md, manual review before execution |
This skill uses these universal patterns:
skills/shared-patterns/state-tracking.mdskills/shared-patterns/failure-recovery.mdskills/shared-patterns/exit-criteria.mdskills/shared-patterns/todowrite-integration.mdApply ALL patterns when using this skill.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.
Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.