popoffvg/plan-context
skills/plan-context/SKILL.md
C4 Level 1 (Context) planning phase: define system boundaries, external actors, integrations, and scope decisions.
$ install --global
skillsauthnpx skillsauth add popoffvg/dotfiles plan-contextInstall 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 AM101.1s1 file scanned
SKILL.md
- name:
- plan-context
- description:
- C4 Level 1 (Context) planning phase: define system boundaries, external actors, integrations, and scope decisions.
plan-context — C4 Level 1 (Context)
Define the system's place in the world before diving into internals.
Inputs
- User's task description or feature request
- Existing
_notes/plan.md(if resuming)
Deliverables
Write or update these sections in _notes/plan.md:
Description
One paragraph: what the system/feature does, who it serves, why it exists.
Glossary (seed)
Extract initial domain entities from the description. Each entry:
**<Term>** — <One-sentence definition in domain language>
context: <Bounded context or module>
aliases: <Alternative names if any>
Rules:
- Use domain language, not implementation jargon (
Order, notOrderDTO). - Ambiguous terms must specify their bounded context.
Context Decisions
For each, capture as a Decision entry:
| Question | Decision | |---|---| | What is in scope? | ... | | What is explicitly out of scope? | ... | | Who are the external actors (users, systems)? | ... | | What external systems do we integrate with? | ... | | What are the trust boundaries? | ... |
Format:
- D1 [L1, fixed]: <decision statement>
rationale: <why>
Acceptance Criteria (initial)
Write verifiable criteria as checkboxes. These may be refined in later phases.
Exit condition
All L1 decisions are fixed. No open questions remain at this level. Glossary seeded. Proceed to L2 (plan-container) or skip to the appropriate level.
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