Run any Skill in Manus with one click

aidd-flow-state

Stars5

Forks0

UpdatedApril 21, 2026 at 04:23

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

GrinRus

GrinRus/ai_driven_dev

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

18 files

SKILL.md

readonly

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-docio and feature-dev-aidd:aidd-loop.

Canonical shared Python entrypoints

python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_feature.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_stage.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/prd_check.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/progress.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/progress_cli.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/tasklist_check.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/tasks_derive.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/stage_result.py
python3 ${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 --stage is 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.v1 artifact under aidd/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).

More from this repository

same repository

aidd-core

GrinRus/ai_driven_dev

Aggregates shared runtime navigation and cross-skill ownership links. Use when resolving shared runtime entrypoints or ownership boundaries. Do not use when the request belongs to `aidd-policy` output/question rules or `status` summary reporting.

2026-04-215

aidd-docio

GrinRus/ai_driven_dev

Owns shared DocIO runtime for markdown slicing/patching, actions validation/apply, and context-map expansion. Use when stage skills need canonical DocIO operations. Do not use when the request primarily belongs to `aidd-flow-state` lifecycle updates or `aidd-core` ownership routing.

2026-04-215

aidd-init

GrinRus/ai_driven_dev

Initializes AIDD workspace scaffolding for the current project. Use when bootstrapping canonical `aidd/` templates and project-owned test execution contract in `aidd/config/gates.json`. Do not use when the request is to start feature ideation (`idea-new`) or to inspect existing ticket progress (`status`).

2026-04-215

aidd-loop

GrinRus/ai_driven_dev

Enforces loop-mode discipline for implement/review/qa (packs, scope, no questions). Use when loop stages require bounded scope and retry policy. Do not use when direct stage execution belongs to `implement`, `review`, or `qa` stage skills.

2026-04-215

aidd-observability

GrinRus/ai_driven_dev

Owns shared observability/runtime reporting for diagnostics, inventory, identifiers, logs, and DAG export. Use when deterministic diagnostics or inventory exports are required. Do not use when request scope is `status` stage summaries or `aidd-core` runtime ownership mapping.

2026-04-215

aidd-rlm

GrinRus/ai_driven_dev

Owns shared RLM evidence workflow for subagents (slice, build, verify, finalize, pack). Use when preload roles require canonical RLM evidence operations. Do not use when the request is stage-local research execution in `researcher` or stage handoff-only guidance in `aidd-stage-research`.

2026-04-215

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-docio and feature-dev-aidd:aidd-loop.

Canonical shared Python entrypoints

python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_feature.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/set_active_stage.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/prd_check.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/progress.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/progress_cli.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/tasklist_check.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/tasks_derive.py
python3 ${CLAUDE_PLUGIN_ROOT}/skills/aidd-flow-state/runtime/stage_result.py
python3 ${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 --stage is 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.v1 artifact under aidd/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).