Turn an analyzed request into an implementation-ready plan, optionally backed by a GitHub issue. Use when the user invokes $plan or continues the Melvyn workflow.
Scanned 9/5/2026
Install to Claude Code
Skills Directorynpx -y skills add twikus/claude-configuration --skill plan --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Plan?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/twikus-plan)More formats (shields.io, HTML) on the badges page.
---
name: plan
description: Turn an analyzed request into an implementation-ready plan, optionally backed by a GitHub issue. Use when the user invokes $plan or continues the Melvyn workflow.
disable-model-invocation: true
argument-hint: "<analysis or request>"
---
Turn the current analysis into one implementation-ready plan.
Include the problem, desired behavior, scope, out of scope, implementation decisions, measurable acceptance criteria, and verification requirements. Prefer behavioral requirements over file paths or code snippets.
Return a focused plan directly. Create a durable GitHub issue when the user requests it, repository rules require it, or the plan is large enough to need tracking.
A plan needs an issue when any of these apply:
- it has at least three independent implementation units;
- it spans multiple subsystems or owners;
- it includes a migration, deployment, or external coordination;
- it is unlikely to finish in one focused implementation session.
When an issue is needed, follow the repository's GitHub attribution rules, create or update it within the authorized scope, read it back, and return its URL with the plan. GitHub availability must not block a focused plan that does not need an issue.
Do not implement the plan.
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!
Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.
Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.
Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.
