act70255/concise-planning
planning/skills/concise-planning/SKILL.md
Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
testing
Updated Mar 29, 2026
$ install --global
skillsauthnpx skillsauth add act70255/skillsbundle concise-planningInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 31, 2026, 10:46 PM65.0s1 file scanned
SKILL.md
- name:
- concise-planning
- description:
- Use when a user asks for a plan for a coding task, to generate a clear, actionable, and atomic checklist.
- risk:
- unknown
- source:
- community
- date_added:
- 2026-02-27
Concise Planning
Goal
Turn a user request into a single, actionable plan with atomic steps.
Workflow
1. Scan Context
- Read
README.md, docs, and relevant code files. - Identify constraints (language, frameworks, tests).
2. Minimal Interaction
- Ask at most 1–2 questions and only if truly blocking.
- Make reasonable assumptions for non-blocking unknowns.
3. Generate Plan
Use the following structure:
- Approach: 1-3 sentences on what and why.
- Scope: Bullet points for "In" and "Out".
- Action Items: A list of 6-10 atomic, ordered tasks (Verb-first).
- Validation: At least one item for testing.
Plan Template
# Plan
<High-level approach>
## Scope
- In:
- Out:
## Action Items
[ ] <Step 1: Discovery>
[ ] <Step 2: Implementation>
[ ] <Step 3: Implementation>
[ ] <Step 4: Validation/Testing>
[ ] <Step 5: Rollout/Commit>
## Open Questions
- <Question 1 (max 3)>
Checklist Guidelines
- Atomic: Each step should be a single logical unit of work.
- Verb-first: "Add...", "Refactor...", "Verify...".
- Concrete: Name specific files or modules when possible.
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
Related Skills
act70255/verification-before-completion
data-ai
VerifiedTrustedCommunity
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evide...
SKILL.mdUpdated Mar 29, 2026
act70255/testing-qa
tools
VerifiedTrustedCommunity
Comprehensive testing and QA workflow covering unit testing, integration testing, E2E testing, browser automation, and quality assurance.
SKILL.mdUpdated Mar 29, 2026
act70255/scout-regiment-workflow-lite
tools
VerifiedTrustedCommunity
evidence-driven proactive engineering workflow: keep momentum, avoid idle loops, require verifiable progress, and escalate blockers with structure.
SKILL.mdUpdated Mar 29, 2026
act70255/playwright-skill
tools
VerifiedTrustedCommunity
Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to /tmp. Test pages, fill forms, take screenshots, check responsive design, validate UX, test login ...
SKILL.mdUpdated Mar 29, 2026