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/improve-claude-local
tools
VerifiedTrustedCommunity
Improve a whole CLAUDE.local.md — the private, per-project rules captured from user corrections. Wraps each conditional rule in a <task-relevant> block so it only surfaces for matching work, merges duplicates, generalizes one-off facts, drops stale entries, and routes raw project facts to engram. Use when the user says "improve claude.local", "clean up the local rules", "claude.local is bloated", or after the Stop hook has appended many rules.
2SKILL.mdUpdated Jun 25, 2026
popoffvg/workflow
testing
VerifiedTrustedCommunity
WM pipeline and conventions shared across all phases. Agents must read this before spec, impl, or verify work.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/code
development
VerifiedTrustedCommunity
One entry point for spec writing, implementation, and bug fixing. Default is new (write spec → grill loop → produce notes → author TODO bodies). Other subcommands: verify (audit), revise (sync to shipped), prototype (settle a decision), code-map (diagram), impl (execute one TODO), fix (analyze cause, correct thoughts, fix behavior), help (this page). Invoke as /code <subcommand>.
2SKILL.mdUpdated Jun 19, 2026
popoffvg/red-green-refactor
development
VerifiedTrustedCommunity
Red-Green-Refactor cycle for bug fixes. Before fixing a bug, first write a failing test that reproduces it (Red), then make the minimal change to pass (Green), then clean up the code (Refactor). Use on any bug fix, error correction, failing test repair, or when user says "fix this bug".
2SKILL.mdUpdated Jun 18, 2026