brutal-plan

Name: brutal-plan
Availability: InStock
Author: Emil

Coordinate multi-perspective planning to produce a workspace plan and implementation tasks.

2|Updated Feb 9, 2026

Search Tags:#planning #requirements #project-management #stakeholders #task-generation #feature-planning

Ready to run

npx skills add https://github.com/sssemil/SKILLS --skill brutal-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: brutal-plan
Source: https://github.com/sssemil/SKILLS/tree/main/brutal-plan
Command: npx skills add https://github.com/sssemil/SKILLS --skill brutal-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates collaborative, multi-perspective feature planning to produce a workspace plan and implementation tasks.

Core Features & Use Cases

Collaborative planning: coordinates input from diverse stakeholders and surfaces gaps in requirements.
Output artifacts: produces a workspace plan document and a concrete set of implementation tasks ready for execution.
Use Case: teams planning a complex feature align on scope, risks, and required steps before code begins.

Quick Start

Provide a high-level feature request to kick off the planning workflow and generate a plan.

Frequently Asked Questions about brutal-plan

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

FAQPage Schema

How do I generate implementation tasks from high-level feature requirements?▼

To generate implementation tasks, provide a high-level feature request to initiate the structured planning workflow. The system interrogates requirements from multiple stakeholder perspectives and outputs a workspace plan alongside concrete tasks ready for execution.

What is collaborative feature planning and when do I need it for project management?▼

Collaborative feature planning coordinates input from diverse stakeholders to surface gaps in requirements before development begins. You need it when planning complex features that require rigorous requirements interrogation to align scope and risks across teams.

Can I use this planning workflow to align stakeholders before writing code?▼

Yes, the planning workflow is designed for teams planning a complex feature to align on scope, risks, and required steps before code begins. It gates risks and interrogates requirements to ensure stakeholders reach consensus prior to implementation.

What's the best way to surface gaps in product requirements during feature planning?▼

The best way to surface requirement gaps is through a structured planning workflow with dedicated interrogation steps. By loading context and rigorously questioning requirements from multiple perspectives, missing scope and risks are identified before execution.

Does multi-perspective project planning work for complex feature scoping without dependencies?▼

Yes, multi-perspective project planning works for complex feature scoping without external dependencies. It implements a structured workflow internally to coordinate stakeholder input, gate risks, and generate a workspace plan and implementation tasks independently.