workflow-feature

Name: workflow-feature
Availability: InStock
Author: akourmaz

Enforce a multi-phase feature workflow with Plan.md, Research.md, and ADRs.

Updated Mar 2, 2026

Search Tags:#workflow #planning #documentation #review #process #stakeholders

Ready to run

npx skills add https://github.com/akourmaz/translate2 --skill workflow-feature

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow-feature
Source: https://github.com/akourmaz/translate2/tree/main/.agents/skills/workflow-feature
Command: npx skills add https://github.com/akourmaz/translate2 --skill workflow-feature

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The protocol standardizes and accelerates the process of introducing new features by providing a clear, auditable workflow from gathering requirements to review and deployment.

Core Features & Use Cases

Requirement gathering, scope definition, and impact assessment for new functionality.
Phase-based planning with Plan.md creation, risk analysis, and acceptance criteria.
Delegation workflow to coder, reviewer, and role-meta-architect, with gated approvals and documentation updates.
Use Case: When introducing a new API endpoint or UI component, teams follow this workflow to ensure alignment and traceability.

Quick Start

Initiate a new feature workflow by outlining the scope, creating a Plan.md, and selecting the required reviewers to begin the phased process.

Frequently Asked Questions about workflow-feature

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

FAQPage Schema

How do I standardize feature planning from requirements to deployment for complex projects?▼

Standardize feature planning by enforcing a multi-phase workflow that includes requirement gathering, risk assessment, and plan creation. This ensures traceable, auditable feature delivery across complex product and engineering teams handling architecture changes and APIs.

What is the best way to document architecture changes and API features during development?▼

Document architecture changes and API features by creating structured Plan.md files, Research.md notes, and ADRs when needed. This protocol enforces documentation updates throughout gated approvals to maintain alignment and traceability.

How do I enforce gated approvals and reviewer delegation for new functionality?▼

Enforce gated approvals and reviewer delegation by using STOP gates within the feature workflow. The protocol delegates tasks to coders, reviewers, and role-meta-architects to ensure structured, auditable approvals before proceeding.

When do I need to create ADRs and STOP gates for feature delivery?▼

Create ADRs and STOP gates when introducing new functionality that requires risk assessment and impact analysis. These gated approvals ensure stakeholder alignment and traceable delivery for APIs, UI components, and architecture changes.

How do I define scope and acceptance criteria for a new API endpoint or UI component?▼

Define scope and acceptance criteria by initiating a feature workflow that outlines requirements and creates a Plan.md. This phase-based planning includes risk analysis to ensure alignment across stakeholders before development begins.