popoffvg/plan-component
skills/plan-component/SKILL.md
C4 Level 3 (Component) planning phase: define internal modules, responsibilities, interfaces, and dependency decisions.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles plan-componentInstall 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 20, 2026, 4:44 AM119.0s1 file scanned
SKILL.md
- name:
- plan-component
- description:
- C4 Level 3 (Component) planning phase: define internal modules, responsibilities, interfaces, and dependency decisions.
plan-component — C4 Level 3 (Component)
Design the internal structure of each container — modules, packages, interfaces.
Prerequisites
All L1 and L2 decisions must be fixed.
Deliverables
Update _notes/plan.md with:
Component Decisions
| Question | Decision | |---|---| | What packages/modules exist in each container? | ... | | What are their responsibilities? | ... | | What interfaces do they expose? | ... | | What are the dependency directions? | ... | | What patterns apply? (repository, service, handler) | ... |
Format:
- D20 [L3, fixed]: <decision statement>
rationale: <why>
Glossary (extend)
Add domain terms for internal concepts (aggregates, value objects, services). Every domain noun used in TODOs must have an entry.
TODOs (L3)
Create TODOs for component-level work (module creation, interface definition, wiring):
- [ ] T20: ...
- level: L3
- files: `path/to/file`
- criteria: AC...
- decisions: D20
Exit condition
All L3 decisions are fixed. No open questions at this level. No contradiction with L1/L2 decisions. Proceed to L4 (plan-code).
Related Skills
popoffvg/test-set-write
testing
VerifiedTrustedCommunity
Use when the user asks to create test sets, enumerate scenarios, generate edge cases, or draft a coverage matrix before implementation.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-set-verify
testing
VerifiedTrustedCommunity
Use when the user asks to review, audit, score, or validate test sets for missed cases before execution or merge.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-harness-plugin
tools
VerifiedTrustedCommunity
Test harness plugins in isolation using tmux panes. Runs MCP servers, unit tests, typecheck, and Claude plugin loading. Use when user says "test plugin", "check plugin", "run plugin tests", "validate plugin", or names a specific plugin to test.
2SKILL.mdUpdated Jun 2, 2026
popoffvg/test-bdd
development
VerifiedTrustedCommunity
Guide for designing integration and e2e tests using BDD (Behavior-Driven Development) methodology with Cucumber-style Given/When/Then scenarios. Use when writing or reviewing tests for any service, API, or component. Language-agnostic — covers scenario structure, step notation, assertion principles, async patterns, and common anti-patterns.
2SKILL.mdUpdated Jun 2, 2026