ao-cyber-systems/plan-objective
plugins/devflow/skills/plan-objective/SKILL.md
Create a detailed execution plan for an objective, breaking it into concrete tasks with success criteria. Use when the user wants to plan an objective, create execution plans, or prepare for building. Triggers on: "plan objective", "create plans", "plan the next objective", "let's plan", "prepare objective", "make plans for"
development
Updated May 5, 2026
$ install --global
skillsauthnpx skillsauth add ao-cyber-systems/devflow-claude plan-objectiveInstall 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 5, 2026, 4:01 AM245.1s1 file scanned
SKILL.md
- name:
- plan-objective
- description:
- |
- Triggers on:
- plan objective", "create plans", "plan the next objective", "let's plan", "prepare objective", "make plans for
- argument-hint:
- [objective] [--auto] [--research] [--skip-research] [--gaps] [--skip-verify] [--work TYPE] [--tdd POSTURE] [--depth LEVEL] [--model PROFILE]
- agent:
- planner
<objective>
Create executable objective prompts (JOB.md files) for a roadmap objective with integrated research and verification.
Default flow: Research (if needed) → Plan → Verify → Done
Orchestrator role: Parse arguments, validate objective, research domain (unless skipped), spawn planner, verify with job-checker, iterate until pass or max iterations, present results. </objective>
<execution_context> @~/.claude/devflow/workflows/plan-objective.md @~/.claude/devflow/references/ui-brand.md </execution_context>
<context> Objective number: $ARGUMENTS (optional — auto-detects next unplanned objective if omitted)Flags:
--research— Force re-research even if RESEARCH.md exists--skip-research— Skip research, go straight to planning--gaps— Gap closure mode (reads VERIFICATION.md, skips research)--skip-verify— Skip verification loop
Intent override flags (one-shot overrides for the resolved (kind, work) configuration):
--work TYPE— Overrideworkfor this objective. Valid:feature | port | refactor | foundation | bugfix | prototype | spike--tdd POSTURE— Override TDD posture:strict | per-feature | skip--depth LEVEL— Override planning depth:quick | standard | comprehensive--model PROFILE— Override model profile:quality | balanced | budget
When any intent override flag is set, the planner persists the override to .planning/objectives/<id>/OBJECTIVE.md so future executor runs honor it.
Normalize objective input in step 2 before any directory lookups. </context>
<process> Execute the job-objective workflow from @~/.claude/devflow/workflows/plan-objective.md end-to-end. Preserve all workflow gates (validation, research, planning, verification loop, routing). </process>Related Skills
ao-cyber-systems/decide
development
VerifiedTrustedCommunity
Resolve a parked decision and resume autonomous execution. Use when you see a pending DECISION-NNN.md in .planning/decisions/pending/, when the user wants to choose an option for a blocked checkpoint:decision, or when you need to tell the executor which option to take. Triggers on: "resolve decision", "decide DECISION-", "pick option for DECISION-", "unblock DECISION-", "answer DECISION-", "choose option for decision", "I want option-a", "go with option-b", "my answer is".
SKILL.mdUpdated Jun 13, 2026
ao-cyber-systems/flow
development
VerifiedTrustedCommunity
Orchestrate a multi-step DevFlow workflow by chaining skills. Use when the user wants to invoke a sequence of skills as one ask (e.g., "build and sync to github", "research, plan, then build", "ship and announce"). Triggers on: "ship X to Y", "build and X", "plan and X", "X then Y", "in one go", "as a chain", "all in sequence", "chain", "ship-and-sync", "research-plan-build"
SKILL.mdUpdated May 26, 2026
ao-cyber-systems/new-monorepo
testing
VerifiedTrustedCommunity
Stamp a new polyglot monorepo using the AO Cyber Systems scaffold — root CLAUDE.md with Layout table, per-area CLAUDE.md, path-filtered CI workflows, comprehensive .gitignore, and the no-binaries pre-commit hook config. Use this for new product monorepos (the 5-monorepo architecture: aodex, aosentry, eden-biz, politihub, aohealth, plus future ones). Triggers on: "new monorepo", "scaffold a monorepo", "set up a monorepo", "create a new product monorepo".
SKILL.mdUpdated May 12, 2026
ao-cyber-systems/monorepo-doctor
development
VerifiedTrustedCommunity
Validate that a monorepo follows the AO Cyber Systems layout convention — root CLAUDE.md declares every area, every area has its own CLAUDE.md, no compiled binaries are tracked in git. Reads the root `CLAUDE.md` Layout table, walks the working tree, and reports drift in a single Markdown summary. Standalone — works on any repo. Triggers on: "audit monorepo layout", "monorepo doctor", "is this monorepo healthy?", "check the layout", "find binaries in the repo".
SKILL.mdUpdated May 12, 2026