How do I install the Aidd Flow State skill?

Run npx skillmds add majiayu000/aidd-flow-state in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aidd Flow State safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aidd Flow State?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aidd Flow State free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aidd Flow State?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aidd Flow State by majiayu000 — Agent Skill

Name: Aidd Flow State
Rating: 4.5 (4 reviews)
Author: majiayu000

Aidd Flow State

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.

majiayu000 cb7ab47 2 files · 3.8 KB Updated Sep 9, 2026 567 repo stars

File contents

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).

---name: aidd-flow-statedescription: 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.--- ## 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](references/progress-tasklist.md) (when: progress/tasklist checks are unclear; why: align check/normalize and logging semantics). - [references/stage-lifecycle.md](references/stage-lifecycle.md) (when: stage result/status flow is unclear; why: keep stage-result and summary updates deterministic).

Frequently asked questions