athal7/plan
skills/plan/SKILL.md
Present a plan and wait for user approval before implementing — load when a change spans multiple files or involves design decisions
$ install --global
skillsauthnpx skillsauth add athal7/dotfiles planInstall 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: May 1, 2026, 2:09 AM129.2s1 file scanned
SKILL.md
- name:
- plan
- description:
- Present a plan and wait for user approval before implementing — load when a change spans multiple files or involves design decisions
- license:
- MIT
- compatibility:
- opencode
Skip for typo fixes, single-line config changes, and trivial one-file edits.
-
Research. Explore the codebase, read relevant files, check git history. Use available capabilities (issues, meetings, logs) to gather context. Only ask the user when information isn't discoverable.
-
Design prerequisite check. For any change touching domain logic, authorization, state machines, or anything enforced in more than one layer — read the relevant code and answer:
- Scattered enforcement: is this concept already checked in multiple places? List callsites. If yes, is centralizing first a prerequisite?
- Coupling: does this add a new dependency between modules that had no prior relationship?
- Extensibility: is this the 2nd or 3rd instance of a pattern? Is there a single abstraction that serves all of them?
If a prerequisite refactor would simplify the work, surface it: propose a separate issue/PR, get user confirmation, do it first.
-
Present the plan in chat. Include: files that will change and why; approach and key decisions; risks or open questions; the first failing test you will write.
-
After approval, implementation begins with the first failing test, strict red/green/refactor.
Related Skills
athal7/zoom
development
VerifiedTrustedCommunity
Zoom meeting captions — file locations and format
6SKILL.mdUpdated May 24, 2026
athal7/dictation
tools
VerifiedTrustedCommunity
macOS dictation custom vocabulary — sync knowledge base names and terms to the system spelling dictionary
6SKILL.mdUpdated May 24, 2026
athal7/knowledge-base
testing
VerifiedTrustedCommunity
Look up people, projects, products, and decisions locally first: contact info (email, Slack ID, GitHub handle), titles and teams, project/product status, who works on what, and past decisions. Check before searching Slack, email, calendar, or GitHub — this is the first stop for any contact detail, project context, or decision-history question.
6SKILL.mdUpdated May 21, 2026
athal7/communication
testing
VerifiedTrustedCommunity
Communication style, audience awareness, and AI-authorship markers for human-facing prose — load when composing chat messages, review comments, merge request descriptions, emails, doc bodies, or ticket descriptions
6SKILL.mdUpdated May 21, 2026