skills.rest
yogata
yogataCOMMUNITY
Explore all skills by this author →
GitHub

agentdev-workflow-lifecycle

Defines workflow phases, work_type classification, and scale criteria for agentdev command pipelines.

Updated Mar 7, 2026
Search Tags:#workflow lifecycle#scale assessment#agentdev#work_type classification#ssot transitions#command pipeline#stage handoff
One-click install
npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-workflow-lifecycle-yogata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentdev-workflow-lifecycle
Source: https://github.com/yogata/agent-dev-flow/tree/main/src/opencode/skills/agentdev-workflow-lifecycle
Command: npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-workflow-lifecycle-yogata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It provides a single declarative source for the AgentDevFlow development workflow, so every agentdev command resolves phase transitions, work_type classification, and scale assessment consistently instead of duplicating judgment logic. ## Core Features & Use Cases - Workflow Phase Definitions: Maps SSoT transitions (req_draft → Issue → PR → merged PR + closed Issue) across req-define, case-open, case-ready, case-run, and case-close. - work_type and Scale Classification: Classifies work as bugfix, maintenance, docs_chore, or feature, and promotes feature scale to large when signals like 10+ affected files or 30+ changes appear. - Structured Stage Handoff: Defines the structured_context serialization contract and source/projection reference resolution policy for passing context between workflow stages. - Use Case: When running /agentdev/case-open, the prepare STEP consults this skill to determine the work_type route and whether the feature requires a large-scale OU/child-Issue structure. ## Quick Start Ask the agent to determine the work_type and command route for a new requirement using the agentdev workflow lifecycle definitions.

Frequently Asked Questions about agentdev-workflow-lifecycle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I classify work_type in an agentdev workflow?▼

Classify work as bugfix, maintenance, docs_chore, or feature using the criteria in this skill. All work_types follow the standard GitHub Issue and PR route; feature additionally passes through case-ready for Definition readiness.

When does a feature become large scale in AgentDevFlow?▼

A feature is promoted to large when it spans multiple REQs, adds many requirement lines, or shows implementation scope signals such as more than 10 affected files or more than 30 individual changes in the draft.

What is the difference between source and projection references?▼

Source is the canonical original under src/opencode/, while projection is the runtime copy under .opencode/. The reference resolution policy selects which to read based on execution purpose: content confirmation, runtime verification, or consistency checking.

Does this skill execute agentdev commands directly?▼

No. It owns no workflow STEP itself; it provides declarative definitions that each command's workflow skill references during prepare and transition STEPs. Command execution logic lives in the individual command definitions.

What happens when agentdev_handoff is true in a consumer repository?▼

In consumer repositories, case-open and case-run stop without creating Issues or starting implementation, reporting the item for manual intake into the agent-dev-flow repository. Self-hosting repositories process it as normal workflow input.

Related Skills

Explore More Software Engineering Skills→
amingclawdevamingclawdev
26

aming-claw-project-inbox

Capture raw user requirements and coordinate Capture and Confirmation modes for backlog promotion via governance endpoints.

Community
Intermediate
storyclaw-officialstoryclaw-official

gh-issues

Orchestrate parallel sub-agents to fix GitHub issues and open pull requests.

Official
Advanced
GGEduGGEdu

requirements-stride

Generate C4 diagrams and STRIDE threat models for architecture risk analysis.

Community
Advanced
ql-linkql-link
5

cowork-issue-sync

Create Linear main records with mirrored GitHub issues and bidirectional links.

Official
Advanced