Use when generating AI cover images or illustrations via OpenRouter API (AI image, OpenRouter, cover image, WeChat, text-to-image, Gemini, image generation).

2026-03-259

execution-workflow

LazyWorkshopCreate/agent-based-workflow

Use when an approved delivery slice or plan exists and the next step is execution, or when debugging, TDD, E2E acceptance, parallel task coordination, or isolated workspace setup is needed (approved slice, approved plan, coordinated execution, implementation execution, worktree, isolated workspace, branch isolation, plan execution, TDD, test first, failing test, bugfix, regression proof, E2E, end-to-end, acceptance test, test suite, acceptance gate, parallel agents, subagent, independent task, coordinator, debugging, root cause, unexpected behavior, verification failure).

2026-03-259

design-workflow

LazyWorkshopCreate/agent-based-workflow

Use when drafting or revising technical design, API endpoint contracts, or advancing a service from evidence into design and implementation readiness (technical design, backend design, platform design, module boundary, API design, endpoint contract, validation, error code, service delivery, design closure, implementation readiness).

2026-03-259

discovery-workflow

LazyWorkshopCreate/agent-based-workflow

Use when researching a topic, discovering or clarifying requirements, tracing evidence, or investigating a technical spike (research, investigation, topic research, technology evaluation, domain analysis, findings report, requirements discovery, elicitation, requirements document, feature definition, use case analysis, requirement clarification, scope definition, acceptance, functional boundary, evidence trace, traceability, data mapping, reference mapping, technical spike, evidence gap, option comparison).

2026-03-259

planning-workflow

LazyWorkshopCreate/agent-based-workflow

Use when splitting scope into executable implementation slices, or when strengthening test and acceptance coverage (implementation breakdown, delivery slices, task decomposition, test breakdown, acceptance, integration test, verification planning).

2026-03-259

generate-mermaid-flowchart

LazyWorkshopCreate/agent-based-workflow

Use when rendering Mermaid syntax into diagram image files for docs or articles (mermaid, flowchart, diagram, PNG, SVG, visualization).

2026-03-259

name	document-lifecycle-workflow
description	Use when renaming, moving, archiving, or cleaning up docs (archive, move, rename documents).
argument-hint	Action to perform, e.g.: archive obsolete analysis pack, rename design doc, sync template references
user-invocable	true

Document Lifecycle Workflow

When to Use

Need to move, rename, archive, or replace documentation
Need to synchronize README entries, cross references, or template references after a document move
Need to keep active docs aligned with the current live layout

Delegation Defaults

Keep the parent agent responsible for classifying the lifecycle action and performing the move, rename, archive, or replace operation itself.
After the target path changes, prefer the Document Ref Cleanup Executor subagent for README, index, prompt, skill, and in-body reference cleanup.

Procedure

Determine whether the task is a move, rename, archive, or active-layout cleanup.
Classify the target document using docs/README.md: design, decisions, plans, status, reference, or archive.
Keep active docs in English.
When archiving, place files under docs/archive/YYYYMM/ and prefix filenames with YYYYMMDD_.
Keep archive month folders flat. Do not recreate legacy subtrees inside docs/archive/.
After the lifecycle action is decided, prefer the Document Ref Cleanup Executor subagent for stale-reference cleanup when that asset is available.
Update README entries, index files, and in-body references after every move or rename.
Search the repository for the old file name or path and remove stale references.
Do not move archived documents back into the active layout without explicit approval.