popoffvg/plan-container
skills/plan-container/SKILL.md
C4 Level 2 (Container) planning phase: define services, databases, protocols, and technology decisions.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles plan-containerInstall 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 AM109.1s1 file scanned
SKILL.md
- name:
- plan-container
- description:
- C4 Level 2 (Container) planning phase: define services, databases, protocols, and technology decisions.
plan-container — C4 Level 2 (Container)
Break the system into deployable containers and decide how they communicate.
Prerequisites
All L1 (Context) decisions must be fixed.
Deliverables
Update _notes/plan.md with:
Container Decisions
| Question | Decision | |---|---| | What services/processes exist? | ... | | What databases/stores are used? | ... | | What message brokers or queues? | ... | | What protocols between containers? (HTTP, gRPC, events) | ... | | What technology choices? (language, framework, runtime) | ... |
Format:
- D10 [L2, fixed]: <decision statement>
rationale: <why>
Glossary (extend)
Add any new domain terms discovered at this level. Review existing entries for accuracy.
Acceptance Criteria (refine)
Add or refine criteria that relate to container boundaries, SLAs, or integration contracts.
TODOs (L2)
Create TODOs for container-level work (infrastructure, configuration, API contracts):
- [ ] T10: ...
- level: L2
- files: `path/to/file` (if applicable)
- criteria: AC...
- decisions: D10
Exit condition
All L2 decisions are fixed. No open questions at this level. No contradiction with L1 decisions. Proceed to L3 (plan-component).
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