flow-skill-write-dep

Draft structured Development Enhancement Proposals with problem statements, alternatives, and implementation plans.

3|Updated Oct 5, 2025

Search Tags:#technical-writing #stakeholders #risk-analysis #dep #development-proposal #architectural-change

Ready to run

npx skills add https://github.com/korchasa/flow --skill flow-skill-write-dep

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: flow-skill-write-dep
Source: https://github.com/korchasa/flow/tree/main/framework/skills/flow-skill-write-dep
Command: npx skills add https://github.com/korchasa/flow --skill flow-skill-write-dep

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

DEP provides a formal, structured approach to proposing technical changes, ensuring decisions are traceable, justifiable, and aligned with stakeholders across engineering, product, security, and operations.

Core Features & Use Cases

Mandatory sections and a standardized template to capture problem statements, proposed solutions, alternatives, risks, and implementation plans.
Templates support versioning, authorship, reviewers, status, and dates for governance and auditability.
Use Case: When proposing a major architectural change or policy update, a DEP documents the rationale, trade-offs, metrics, and rollout plan to obtain informed consent from stakeholders.

Quick Start

Draft a DEP using the provided template, starting with a clear problem statement and a proposed solution, then fill in risks, alternatives, and an implementation plan.

Frequently Asked Questions about flow-skill-write-dep

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

FAQPage Schema

How do I write a Development Enhancement Proposal for an architectural change?▼

To write a Development Enhancement Proposal, draft a problem statement with contextual data, propose solutions, detail alternatives with trade-offs, assess risks with mitigations, and define an actionable implementation plan to align stakeholders.

What should be included in a technical proposal for stakeholder alignment?▼

A technical proposal for stakeholder alignment should include a clear problem statement, proposed solutions, alternatives with trade-offs, a technical design section, risk mitigations, an implementation plan, and governance metadata like author, status, and review dates.

When do I need a formal development proposal instead of a standard ticket?▼

You need a formal development proposal when proposing major technical changes or policy updates, ensuring decisions are traceable, justifiable, and aligned across engineering, product, security, and operations teams through documented rationale and rollout plans.

How do I structure risk analysis and alternatives in a technical design document?▼

Structure risk analysis by identifying specific risks paired with actionable mitigations, and document alternatives by outlining different approaches alongside their respective trade-offs and decision criteria within the technical design section.

Does a DEP template support versioning and governance metadata for review tracking?▼

Yes, a DEP template supports governance and auditability by capturing versioning, authorship, reviewers, status, and review dates, ensuring technical changes remain traceable and justifiable throughout the decision lifecycle.