ao-cyber-systems/list-objective-assumptions
plugins/devflow/skills/list-objective-assumptions/SKILL.md
See what Claude plans to do for an objective before it starts, so you can course-correct early. Shows the intended approach without creating any files.
tools
Updated May 5, 2026
$ install --global
skillsauthnpx skillsauth add ao-cyber-systems/devflow-claude list-objective-assumptionsInstall 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, 3:57 AM58.6s1 file scanned
SKILL.md
- name:
- list-objective-assumptions
- description:
- |
- argument-hint:
- [objective]
- disable-model-invocation:
- true
<objective>
Analyze an objective and present Claude's assumptions about technical approach, implementation order, scope boundaries, risk areas, and dependencies.
Purpose: Help users see what Claude thinks BEFORE planning begins - enabling course correction early when assumptions are wrong. Output: Conversational output only (no file creation) - ends with "What do you think?" prompt </objective>
<execution_context> @~/.claude/devflow/workflows/list-objective-assumptions.md </execution_context>
<context> Objective number: $ARGUMENTS (required)Load project state first: @.planning/STATE.md
Load roadmap: @.planning/ROADMAP.md </context>
<process> 1. Validate objective number argument (error if missing or invalid) 2. Check if objective exists in roadmap 3. Follow list-objective-assumptions.md workflow: - Analyze roadmap description - Surface assumptions about: technical approach, implementation order, scope, risks, dependencies - Present assumptions clearly - Prompt "What do you think?" 4. Gather feedback and offer next steps </process><success_criteria>
- Objective validated against roadmap
- Assumptions surfaced across five areas
- User prompted for feedback
- User knows next steps (discuss context, plan objective, or correct assumptions) </success_criteria>
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