grinrus/aidd-flow-state
skills/aidd-flow-state/SKILL.md
Owns shared flow/state runtime for stage state, progress/tasklist, and stage-result lifecycle. Use when orchestration needs canonical active-stage, progress, tasklist, or stage-result commands. Do not use when the request is about `aidd-docio` action patch mechanics or `status` read-only summaries.
$ install --global
skillsauthnpx skillsauth add grinrus/ai_driven_dev aidd-flow-stateInstall 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 22, 2026, 8:05 PM17.8s18 files scanned
SKILL.md
- name:
- aidd-flow-state
- description:
- Owns shared flow/state runtime for stage state, progress/tasklist, and stage-result lifecycle. Use when orchestration needs canonical active-stage, progress, tasklist, or stage-result commands. Do not use when the request is about `aidd-docio` action patch mechanics or `status` read-only summaries.
- lang:
- en
- model:
- inherit
- user-invocable:
- false
Scope
- This skill owns shared flow/state runtime entrypoints.
- Stage skills call these commands for active stage/feature state, progress checks, tasklist normalization, and stage-result/status lifecycle.
- DocIO and loop orchestration ownership remains in
feature-dev-aidd:aidd-docioandfeature-dev-aidd:aidd-loop.
Canonical shared Python entrypoints
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_feature.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_stage.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/prd_check.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/progress.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/progress_cli.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/tasklist_check.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/tasks_derive.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/stage_result.pypython3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/status_summary.py
Command contracts
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_stage.py
- When to run: at stage entry before stage-local orchestration begins.
- Inputs: stage identifier (canonical positional argument; compatibility alias
--stageis accepted) and optional ticket/feature context. - Outputs: normalized active-stage state in workspace metadata.
- Failure mode: non-zero exit when stage value is invalid or active workspace metadata is unreadable.
- Next action: fix stage/context input and rerun stage activation.
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/stage_result.py
- When to run: stage-chain postflight only after stage runtime + actions apply complete.
- Inputs: canonical stage-result payload (ticket, stage, result, scope/work-item keys, evidence links).
- Outputs: deterministic
aidd.stage_result.v1artifact underaidd/reports/loops/<ticket>/<scope_key>/. - Failure mode: non-zero exit on missing required payload fields or invalid contract values.
- Next action: fix postflight payload generation and rerun stage-chain; do not switch to non-canonical runtime paths.
Ownership guard
- Flow/state command runtime modules must live under
skills/aidd-flow-state/runtime/*. - Consumers should use
skills/aidd-flow-state/runtime/*as canonical command paths.
Additional resources
- references/progress-tasklist.md (when: progress/tasklist checks are unclear; why: align check/normalize and logging semantics).
- references/stage-lifecycle.md (when: stage result/status flow is unclear; why: keep stage-result and summary updates deterministic).
Related Skills
grinrus/tasks-new
tools
VerifiedTrustedCommunity
Derives or refines tasklist items from PRD and plan artifacts. Use when tasklist stage prepares implementation-ready work items. Do not use when the request is plan authoring in `plan-new` or loop execution in `implement`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/status
testing
VerifiedTrustedCommunity
Generates consolidated ticket status summary and key artifact pointers. Use when checking current stage state or handoff readiness. Do not use when the request is diagnostics/inventory from `aidd-observability` or flow-state mutation via `aidd-flow-state`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/spec-interview
testing
VerifiedTrustedCommunity
Collects missing spec inputs and synchronizes answers into `spec.yaml`. Use when review-spec leaves unresolved specification fields. Do not use when the request is readiness gating in `review-spec` or task derivation in `tasks-new`.
5SKILL.mdUpdated Apr 5, 2026
grinrus/review
testing
VerifiedTrustedCommunity
Runs review-stage validation for scope changes, findings, and follow-up task derivation. Use when review stage needs verdict and handoff tasks. Do not use when the request is direct implementation execution in `implement` or QA validation in `qa`.
5SKILL.mdUpdated Apr 5, 2026