orinachum/plan
qq/.agent/skills/plan/SKILL.md
Generates a detailed architectural or execution plan and saves it to docs/plan/. Use this ONLY when the user explicitly asks to "plan" or "create a plan".
$ install --global
skillsauthnpx skillsauth add orinachum/autonomous-intelligence 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: Apr 10, 2026, 9:10 AM4.5s1 file scanned
SKILL.md
- name:
- plan
- description:
- Generates a detailed architectural or execution plan and saves it to docs/plan/. Use this ONLY when the user explicitly asks to "plan" or "create a plan".
Plan Generator
This skill captures the user's intent, formulates a comprehensive step-by-step plan, and persists it to a markdown file for documentation and future reference.
When to use this skill
- When the user says "I want to plan".
- When the user says "create a plan" or "draft a plan".
- When the user asks to "plan" a specific feature or refactor.
Instructions
- Analyze Context: Review the conversation history and the user's specific request to understand the scope (e.g., new feature, refactor, bug fix).
- Formulate Plan: Create a structured plan including:
- Objective: High-level goal.
- Context: Why we are doing this.
- Implementation Steps: Detailed breakdown of tasks (files to create, code to modify, commands to run).
- Verification: How to test the plan.
- Generate Filename: Create a descriptive filename with a timestamp to prevent overwrites.
- Format:
docs/plan/YYYY-MM-DD-topic-name.md - Example:
docs/plan/2026-02-01-nova-sonic-integration.md
- Format:
- Write File: Save the formatted plan content to the generated path.
- STOP:
- CRITICAL: Do not execute the plan.
- Do not write code (other than the plan file).
- Confirm to the user: "Plan saved to [filename]." and terminate the turn.
Constraints
- Output Location: MUST be inside
docs/plan/. - Action Limit: ONLY write the plan file. DO NOT implement the steps.
- Tone: Technical, concise, and structured.
Remember
The user request is the plan and save it to docs/plans/*.md *.md is your definition of done and stop after that.
Related Skills
orinachum/test
testing
VerifiedTrustedCommunity
Run TTS round-trip tests — pure-logic unit tests and optional integration tests against live TTS/STT services.
223SKILL.mdUpdated Apr 10, 2026
orinachum/speak
development
VerifiedTrustedCommunity
Speak text aloud using the Magpie TTS container in the realtime-api Docker stack. Zero external dependencies — just curl + aplay.
223SKILL.mdUpdated Apr 10, 2026
orinachum/deploy
development
VerifiedTrustedCommunity
Build and deploy the realtime-api Docker container with full verification that deployed code matches local source.
223SKILL.mdUpdated Apr 10, 2026
orinachum/coding
tools
VerifiedTrustedCommunity
Enhanced coding assistance
223SKILL.mdUpdated Apr 10, 2026