planning-guidelines
Plan safer Portfolio Buddy changes
Portfolio Buddy feature work can drift into risky refactors or mobile gaps. This skill guides Claude, Codex, and Claude Code to plan conservative, responsive changes.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "planning-guidelines" from https://skillstore.io/skills/5minfutures-planning-guidelines.md and its manifest at https://skillstore.io/api/skills/5minfutures-planning-guidelines/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-guidelines". Plan a new dashboard control for starting capital.
Expected outcome:
A concise plan that extends the existing input, checks mobile touch targets, and asks whether the control should appear conditionally.
Using "planning-guidelines". Decide whether to replace a working calculation module.
Expected outcome:
An exception analysis that compares risk, upside, complexity, and approval needs before recommending preservation or targeted change.
Using "planning-guidelines". Prepare questions for ambiguous trading day logic.
Expected outcome:
A structured clarification with recommended and alternate interpretations, including pros, cons, and domain reasoning.
Security Audit
SafeManual review found the static findings are false positives caused by Markdown fences, inline code formatting, and ordinary planning prose. The skill is documentation-only and shows no executable shell commands, network access, credential handling, system reconnaissance, or prompt injection attempt.
Risk Factors
⚙️ External commands (37)
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/5minfutures-planning-guidelines/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/5minfutures-planning-guidelines?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/5minfutures-planning-guidelines?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/5minfutures-planning-guidelines/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/5minfutures-planning-guidelines.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
5MinFutures. (2026). planning-guidelines security audit report (audit version 6) [Author version unspecified]. Skillstore. https://skillstore.io/skills/5minfutures-planning-guidelines/audits/6BibTeX citation
@techreport{5minfutures-5minfutures-planning-guidelines-2026,
author = {5MinFutures},
title = {planning-guidelines security audit report (audit version 6)},
institution = {Skillstore},
year = {2026},
number = {6},
url = {https://skillstore.io/skills/5minfutures-planning-guidelines/audits/6},
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: "planning-guidelines security audit report (audit version 6)"
version: "unspecified"
type: report
authors:
- name: "5MinFutures"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/5minfutures-planning-guidelines/audits/6"
identifiers:
- type: other
value: "skillstore:5minfutures-planning-guidelines:audit:6"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan a safe feature change
Use the guide to preserve working code, identify risks, and request approval before larger changes.
Check responsive design choices
Apply the mobile and desktop checklist before adding UI controls, spacing, or visibility rules.
Standardize requirement gathering
Use the clarifying question format to compare options and explain trade-offs before implementation starts.
Try These Prompts
Use the planning guidelines to plan this small Portfolio Buddy fix: [describe fix]. Preserve existing behavior and list mobile checks.
Use the clarifying question format for this request: [describe request]. Give recommended and alternate options with trade-offs.
Assess whether this proposed improvement meets the low-risk, high-upside, low-complexity criteria: [describe improvement].
Create a Portfolio Buddy implementation plan for [feature]. Include preservation strategy, responsive behavior, approval points, risks, and validation steps.
Best Practices
- Start by identifying existing code that should be preserved.
- Check mobile and desktop behavior before calling a plan complete.
- Ask one clear clarification when requirements affect architecture or user experience.
Avoid
- Replacing working code because a different pattern looks cleaner.
- Adding libraries or abstractions before proving they reduce real complexity.
- Guessing product behavior when a short clarification would prevent rework.
Frequently Asked Questions
What does this skill help with?
Does it write code automatically?
Can it be used outside Portfolio Buddy 2?
When should it ask clarifying questions?
How does it handle refactoring?
Does it include security controls?
Developer Details
Author
5MinFuturesLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/5MinFutures/futures-arena/tree/main/.claude/skills/planning-guidelinesRef
c1fdca50ff516318f65fed0d7f9e82797c5171dc
Maintenance freshness
7/18/2026
Usage
10 downloads · 218 views
File structure
📄 SKILL.md