> **⚠️ DEPRECATED:** This skill has been superseded by the consolidated workflow tracking approach.
Tracks workflow state using the new consolidated approach with per-workflow state files.
/plugin marketplace add marcel-ngan/ai-dev-team/plugin install ai-dev-team@ai-dev-team-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
state-schema.json⚠️ DEPRECATED: This skill has been superseded by the consolidated workflow tracking approach.
Use instead:
skills/workflow/workflow-tracking/State files now live in
.ai-dev-team/workflow/active/{workflow-name}/state.jsoninstead of.ai-dev-team/workflow-state/.
.ai-dev-team/
└── workflow-state/
├── PROJECT-123.json # Per-story state
├── PROJECT-124.json
└── PROJECT-125.json
workflow/
└── active/
└── development-EPIC-45/
├── workflow.md # Workflow manifest
├── state.json # Consolidated state (replaces per-story files)
├── stories/ # Story details
│ ├── PROJECT-123.md
│ └── PROJECT-124.md
└── decisions.md # Decision log
| Aspect | Old | New |
|---|---|---|
| Location | .ai-dev-team/workflow-state/ | .ai-dev-team/workflow/active/{name}/state.json |
| Scope | Per-story | Per-workflow (may contain multiple stories) |
| Related files | Scattered (context/, .ai-dev-team/) | Consolidated in workflow folder |
| Story details | Separate context/stories/*.md | .ai-dev-team/workflow/active/{name}/stories/*.md |
| Cleanup | Manual | Automatic via archival skill |
The state.json schema is largely the same. See skills/workflow/workflow-tracking/SKILL.md for the current schema.
Key additions in new approach:
workflow_id - Workflow folder nameworkflow_type - Type of workflow (development, sprint-planning, etc.)skills/workflow/workflow-tracking/SKILL.md - Current workflow tracking approachskills/workflow/workflow-archival/SKILL.md - Archival and context updatesThe content below is preserved for reference. Do not use this approach for new workflows.
<details> <summary>Original Documentation (Archived)</summary>This skill enabled persistent workflow state tracking for individual stories. Each story had its own state file that tracked current position, gate history, and completed steps.
.ai-dev-team/
└── workflow-state/
├── PROJECT-123.json
├── PROJECT-124.json
└── PROJECT-125.json
See state-schema.json for the JSON schema (still applicable to new state.json format).
Activates when the user asks about AI prompts, needs prompt templates, wants to search for prompts, or mentions prompts.chat. Use for discovering, retrieving, and improving prompts.
Search, retrieve, and install Agent Skills from the prompts.chat registry using MCP tools. Use when the user asks to find skills, browse skill catalogs, install a skill for Claude, or extend Claude's capabilities with reusable AI agent components.
Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.