planning
Plan Feature Work with Clear Implementation Tasks
Feature ideas often fail because requirements and task boundaries stay unclear. This skill turns discovery answers into a structured implementation plan.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "planning" from https://skillstore.io/skills/doyajin174-planning.md and its manifest at https://skillstore.io/api/skills/doyajin174-planning/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 "planning". Plan password reset for an existing web application.
Expected outcome:
- Discovery questions cover identity proof, token expiry, email delivery, abuse limits, and success metrics.
- The plan lists affected account, email, form, and test areas.
- Tasks separate token generation, request flow, reset flow, validation, and user messaging.
Using "planning". Prepare a migration from one payment provider to another.
Expected outcome:
The skill produces a discovery summary, compares migration approaches, lists open risks, and breaks implementation into test-first tasks.
Using "planning". Turn a short feature request into work for a new contractor.
Expected outcome:
The result explains the goal, expected files, required tests, task order, and commit messages in plain language.
Security Audit
SafeAll fourteen static findings are false positives. They are Markdown fenced blocks and an example git commit command inside documentation, with no executable script or automatic external command use. No prompt injection or malicious intent was found in SKILL.md.
Risk Factors
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/doyajin174-planning/audits/8?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/doyajin174-planning?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/doyajin174-planning?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/doyajin174-planning/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/doyajin174-planning.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
Doyajin174. (2026). planning security audit report (audit version 8) [Author version 2.0]. Skillstore. https://skillstore.io/skills/doyajin174-planning/audits/8BibTeX citation
@techreport{doyajin174-doyajin174-planning-2026,
author = {Doyajin174},
title = {planning security audit report (audit version 8)},
institution = {Skillstore},
year = {2026},
number = {8},
url = {https://skillstore.io/skills/doyajin174-planning/audits/8},
note = {Author version 2.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "planning security audit report (audit version 8)"
version: "2.0"
type: report
authors:
- name: "Doyajin174"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/doyajin174-planning/audits/8"
identifiers:
- type: other
value: "skillstore:doyajin174-planning:audit:8"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a new product feature
Turn a feature idea into goals, constraints, decisions, files, tests, and task steps.
Clarify vague stakeholder requests
Use focused questions to identify success measures, limits, alternatives, and unresolved decisions.
Prepare work for another engineer
Create a plan that explains context, file changes, test work, and commit boundaries.
Try These Prompts
Use the planning skill for this feature: [feature idea]. Ask discovery questions first. Wait for my answers before writing a plan.
Use my notes to write a discovery summary. Include core requirements, technical decisions, constraints, alternatives, and open questions.
Create an implementation plan for [feature]. Assume the engineer lacks context. Include goal, stack, affected files, tests, tasks, and commits.
Review this implementation plan for gaps. Make tasks smaller, add missing tests, identify risky assumptions, and preserve clear commit boundaries.
Best Practices
- Answer discovery questions before asking for the final implementation plan.
- Provide repository context when file paths, frameworks, or dependencies matter.
- Review open questions before execution so hidden assumptions do not enter the task list.
Avoid
- Do not skip discovery when the feature goal or success measure is unclear.
- Do not treat example file paths as verified repository paths.
- Do not use the plan as a substitute for security, compliance, or architecture review.
Frequently Asked Questions
Does this skill write code?
When should I use it?
Can it work with Claude, Codex, and Claude Code?
Does it need repository access?
Can it handle non-technical requests?
How detailed are the tasks?
Developer Details
Author
Doyajin174License
MIT
Author version
v2.0
Skillstore revision
r1
Version notice
The author-declared version is not valid SemVer.
Ref
72d5025b022c77f7a51bdf5c1637c689c80e89d1
Maintenance freshness
7/18/2026
Usage
5 downloads · 237 views
File structure
📄 SKILL.md