assisted_workflow

Analyze the codebase and produce architecture.md (tech stack, dependencies, patterns, auth, roles, code metrics) and requirements.md (functional, non-functional, business rules with file references). Use when the user asks to document project architecture, map implemented requirements, or generate a project knowledge base.

Analyze the codebase and produce architecture.md (tech stack, dependencies, patterns, auth, roles, code metrics) and requirements.md (functional, non-functional, business rules with file references). Use when the user asks to document project architecture, map implemented requirements, or generate a project knowledge base.

Execute implementation and validation from approved workflow plans or inline context. Use when a user asks to apply `workflow/plans/{task-name}.md`, provide inline context with scope/criteria/approach, create or update tests for new and impacted behavior, analyze regressions, and report validation evidence.

Build implementation plans from approved requirements in this repository workflow. Use when a user asks to create `workflow/plans/{task-name}.md` from approved requirements, including testing strategy, impact analysis, and regression-risk mitigation.

Execute implementation and validation from approved workflow plans or inline context. Use when a user asks to apply `workflow/plans/{task-name}.md`, provide inline context with scope/criteria/approach, create or update tests for new and impacted behavior, analyze regressions, and report validation evidence.

Build implementation plans from approved requirements in this repository workflow. Use when a user asks to create `workflow/plans/{task-name}.md` from approved requirements, including testing strategy, impact analysis, and regression-risk mitigation.

Create commits for all pending repository changes by strictly following CONTRIBUTING.md commit rules. Use when the user asks to commit changes, organize commits by scope, avoid oversized commits, or enforce Conventional Commits messages in English.

Create commits for all pending repository changes by strictly following CONTRIBUTING.md commit rules. Use when the user asks to commit changes, organize commits by scope, avoid oversized commits, or enforce Conventional Commits messages in English.

Create implementation preparation artifacts from approved requirements. Use when a user asks to convert requirements into a project management issue and generate or create the implementation branch using workflow naming rules.

Analyze feasibility and produce requirement documents for this repository workflow. Use when a user asks to scope a task, validate implementation viability, clarify acceptance criteria/Definition of Done, or create `workflow/requirements/{task-name}.md`.

Create implementation preparation artifacts from approved requirements. Use when a user asks to convert requirements into a project management issue and generate or create the implementation branch using workflow naming rules.

Analyze feasibility and produce requirement documents for this repository workflow. Use when a user asks to scope a task, validate implementation viability, clarify acceptance criteria/Definition of Done, or create `workflow/requirements/{task-name}.md`.

Review delivery adherence and generate summary artifacts. Works independently from git history, with an external reference (URL/inline requirements), or from local workflow files. Use when a user asks to summarize implementation work, compare delivery against requirements, or create `workflow/summaries/{task-name}.md`.

Review delivery adherence and generate summary artifacts. Works independently from git history, with an external reference (URL/inline requirements), or from local workflow files. Use when a user asks to summarize implementation work, compare delivery against requirements, or create `workflow/summaries/{task-name}.md`.