planner
Create Phased Implementation Plans
Complex technical requests can hide dependencies, risks, and unclear requirements. This skill produces phased plans with atomic tasks, acceptance criteria, and validation steps.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "planner" from https://skillstore.io/skills/am-will-planner.md and its manifest at https://skillstore.io/api/skills/am-will-planner/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "planner". Plan adding Google sign-in to an existing web application.
Expected outcome:
A phased plan covering provider configuration, callback routing, user mapping, interface changes, security checks, integration tests, deployment, and rollback.
Using "planner". Plan a fix for duplicate payment webhook processing.
Expected outcome:
An investigation and repair plan covering reproduction, idempotency storage, concurrency behavior, regression tests, monitoring, deployment checks, and rollback.
Using "planner". Plan migrating a shared API client to a new major version.
Expected outcome:
A staged migration plan covering usage discovery, compatibility changes, incremental adoption, contract tests, observability, release gates, and cleanup.
Security Audit
SafeAll four static findings are false positives caused by ordinary prose and Markdown backticks. The skill contains no executable commands, system reconnaissance, prompt injection, or malicious semantic intent.
Risk Factors
⚙️ External commands (3)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/am-will-planner/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/am-will-planner?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/am-will-planner?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/am-will-planner/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/am-will-planner.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
am-will. (2026). planner security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/am-will-planner/audits/5BibTeX citation
@techreport{am-will-am-will-planner-2026,
author = {am-will},
title = {planner security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/am-will-planner/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "planner security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "am-will"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/am-will-planner/audits/5"
identifiers:
- type: other
value: "skillstore:am-will-planner:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a Feature
Convert a feature request into sequenced sprints, atomic tasks, tests, and rollout considerations.
Scope a Bug Fix
Trace a reported defect through likely components and define focused investigation, repair, and regression testing tasks.
Prepare Delivery Work
Create a reviewable delivery plan with dependencies, demonstrations, risks, and acceptance criteria for team coordination.
Try These Prompts
Create an implementation plan for [small change]. Ask essential clarification questions, then provide atomic tasks with acceptance criteria and validation.
Plan the investigation and repair of [bug]. Include affected areas, likely causes, regression tests, risks, and rollback steps.
Create a phased plan for [feature] across [systems]. Map dependencies, integrations, permissions, data changes, tests, deployment, and sprint demonstrations.
Design a phased migration plan from [current state] to [target state]. Include prerequisites, compatibility checks, observability, rollback gates, and parallel work.
Best Practices
- Provide business goals, technical constraints, and measurable success criteria.
- Answer clarification questions before requesting the final plan.
- Review task dependencies, validation steps, and rollback assumptions with implementers.
Avoid
- Do not request a final plan while critical requirements remain unknown.
- Do not treat estimated complexity or sequencing as confirmed implementation facts.
- Do not use the plan as a substitute for testing, review, or deployment controls.