plan-adr-flow — community plan-adr-flow, SourceDoc, community, ide skills

v1.0.0

About this Skill

Ideal for Development Agents requiring structured task planning and technical decision documentation in Markdown files like PLAN.md and docs/ADR/ Plan and document coding tasks with PLAN.md and ADRs in docs/ADR. Use when a task can be decomposed, when asked to create or update PLAN.md, or when capturing technical decisions.

fyuuki0jp fyuuki0jp
[0]
[0]
Updated: 3/12/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
30
Canonical Locale
en
Detected Body Locale
en

Ideal for Development Agents requiring structured task planning and technical decision documentation in Markdown files like PLAN.md and docs/ADR/ Plan and document coding tasks with PLAN.md and ADRs in docs/ADR. Use when a task can be decomposed, when asked to create or update PLAN.md, or when capturing technical decisions.

Core Value

Empowers agents to generate and manage technical decision records in ADR format and task plans in Markdown, streamlining development workflows through organized documentation in `PLAN.md` and `docs/ADR/` files, leveraging Markdown parsing and generation capabilities

Ideal Agent Persona

Ideal for Development Agents requiring structured task planning and technical decision documentation in Markdown files like PLAN.md and docs/ADR/

Capabilities Granted for plan-adr-flow

Automating documentation updates in `PLAN.md`
Generating ADR records for technical decisions
Organizing task planning and implementation details in Markdown files

! Prerequisites & Limits

  • Requires access to repository filesystem for reading and writing `PLAN.md` and `docs/ADR/` files
  • Limited to tasks that are meaningfully decomposable

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is plan-adr-flow?

Ideal for Development Agents requiring structured task planning and technical decision documentation in Markdown files like PLAN.md and docs/ADR/ Plan and document coding tasks with PLAN.md and ADRs in docs/ADR. Use when a task can be decomposed, when asked to create or update PLAN.md, or when capturing technical decisions.

How do I install plan-adr-flow?

Run the command: npx killer-skills add fyuuki0jp/SourceDoc/plan-adr-flow. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for plan-adr-flow?

Key use cases include: Automating documentation updates in `PLAN.md`, Generating ADR records for technical decisions, Organizing task planning and implementation details in Markdown files.

Which IDEs are compatible with plan-adr-flow?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for plan-adr-flow?

Requires access to repository filesystem for reading and writing `PLAN.md` and `docs/ADR/` files. Limited to tasks that are meaningfully decomposable.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add fyuuki0jp/SourceDoc/plan-adr-flow. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use plan-adr-flow immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

plan-adr-flow

Install plan-adr-flow, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

Plan + ADR Flow

Goal

Keep task planning and technical decisions documented in PLAN.md and docs/ADR/... before, during, and after implementation.

Workflow

  1. Triage task size

    • If the task is not meaningfully decomposable, proceed without creating PLAN.md or ADR unless requested.
    • If the task is decomposable, draft a plan and confirm with the user before implementation.
  2. Create plan and ADR when planning

    • Create or replace PLAN.md at repo root with the implementation plan.
    • Create docs/ADR/YYYYMMDD-title.md for the technical decision record before coding.
    • Create docs/ADR/ if missing.
    • Use a short, lowercase, hyphenated slug for title.
  3. Update during implementation

    • Treat PLAN.md as a living memo; update it frequently to reflect reality.
    • Append ADR updates when technical issues or new decisions appear; keep prior entries.
  4. Finalize after implementation

    • Update ADR with outcomes, changes, and follow-ups.
    • Mark PLAN.md as complete or reflect the final state.

ADR template (minimum)

markdown
1# <Title> 2 3Date: YYYY-MM-DD 4Status: Proposed | Accepted | Superseded 5 6## Context 7- <Why this decision is needed> 8 9## Decision 10- <What is decided> 11 12## Consequences 13- <Impact, tradeoffs, follow-ups> 14 15## Change log 16- YYYY-MM-DD: <What changed and why>

Notes

  • Keep ADR updates additive; never delete past entries.
  • Keep PLAN.md specific to the current task; do not modify PLANS.md unless explicitly asked.

Related Skills

Looking for an alternative to plan-adr-flow or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer