skills.rest
dmedina-dev
dmedina-devCOMMUNITY
Explore all skills by this author →
GitHub

brainstorming-workflow

Orchestrate teammate-driven feature development from discovery through PR creation.

1|Updated Mar 29, 2026
Search Tags:#planning#tdd#orchestration#code-review#git-worktrees#teammates#pr-automation
One-click install
npx skills add https://github.com/dmedina-dev/dev-forge --skill brainstorming-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: brainstorming-workflow
Source: https://github.com/dmedina-dev/dev-forge/tree/main/plugins/forge-brainstorming/skills/brainstorming-workflow
Command: npx skills add https://github.com/dmedina-dev/dev-forge --skill brainstorming-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinates complex, cross-cutting feature development where discovery, architecture choices, TDD planning, implementation, deep review, and PR creation must be orchestrated without losing context. It prevents repeated context loss from ephemeral agents by using persistent named teammates and clear gate checkpoints so teams can safely progress through multi-phase work.

Core Features & Use Cases

  • Persistent Teammates: Named agents (scout, architect, builder, reviewer, closer) that retain context across phases for continuous, coherent execution.
  • Gate-driven Workflow: Mandatory and conditional gates (clarifying questions, architecture choice, plan approval, deep-review decisions) to reduce risk and give the user explicit control points.
  • TDD & Review Integration: Generates TDD plans, runs per-task implementation loops with reviewer validation, applies five deep-review lenses, and finishes with PR creation and verification via integrated superpowers skills.
  • Use Case: Deliver a multi-component feature (API + frontend + migrations) by running discovery, choosing an architecture, producing a TDD plan, executing tasks with worktrees, completing deep review, and opening a verified PR.

Quick Start

/brainstorming Describe the new multi-page payments flow and include --auto-plan to generate a TDD plan and begin teammate-driven execution.

Frequently Asked Questions about brainstorming-workflow

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

FAQPage Schema
How do I coordinate cross-team feature development without losing context between phases?▼

Cross-team feature development context is maintained by orchestrating persistent named teammates across discovery, planning, execution, and review phases. Gate-driven checkpoints provide explicit control points so teams can safely progress through multi-component work without repeated context loss.

How do I generate a TDD plan for a multi-component feature?▼

TDD plans are generated during the planning phase by the architect teammate after discovery and architecture choices are approved. The workflow produces a structured test-driven development plan that drives per-task implementation loops with reviewer validation.

What is the best way to automate deep code review before opening a PR?▼

Automated deep code review is handled by applying five deep-review lenses through a dedicated reviewer teammate. The workflow enforces reviewer validation during per-task implementation loops, ensuring PR creation only begins after verified review decisions are made.

Can I use git worktrees to isolate teammate-driven feature execution?▼

Git worktrees are supported natively for isolating teammate-driven feature execution. The workflow manages worktree creation during the execution phase, allowing builder teammates to implement tasks in isolated branches before PR creation and verification.

Does this workflow require manual approval before implementation begins?▼

Manual approval is required through mandatory gate protocols before implementation begins. Users must approve clarifying questions, architecture choices, and TDD plans, giving explicit control over progression from planning to execution phases.

When should I not use a teammate-driven orchestration workflow?▼

Teammate-driven orchestration is not suited for simple, single-component tasks that lack cross-cutting concerns. It is designed for complex multi-component or cross-team feature work requiring persistent context, TDD planning, and gate-driven approvals across multiple phases.

Related Skills

Explore More Software Engineering Skills→
jaydelandjaydeland

gsd-2

Orchestrates spec-driven software development for AI coding agents with git worktrees and crash recovery.

Community
Advanced
mckissingermckissinger
1

land-feature

Coordinate GitHub pull request landing workflows to safely merge verified features into the main branch.

Community
Advanced
AndreJorgeLopesAndreJorgeLopes
1

executing-plans

Route upstream executing-plans workflows into devflow finish-feature verification and PR/MR creation.

Community
Intermediate
cameronraysmithcameronraysmith
14

meta-agent-teams

Orchestrate persistent agent teams with shared task lists and messaging.

Community
Advanced