How do I install the Discuss Subtask skill?

Run npx skillmds@latest add easyinplay/discuss-subtask in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Discuss Subtask safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Discuss Subtask?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Discuss Subtask free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Discuss Subtask?

easyinplay (@easyinplay) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Discuss Subtask by easyinplay — Agent Skill

Name: Discuss Subtask
Author: easyinplay

Discuss Subtask

Stage ①.c 子任务层 discuss sub-workflow — superpowers brainstorming (≥2 approach / 核心算法 / API contract / 错误成本高)。schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available (superpowers-brainstorming + grill-with-docs + grill-me) + 1 phase (01-brainstorm with conditional invokes_tools for spec_ambiguous + no_docs)。Triggered by harnessed CLI `harnessed discuss-subtask --task <text>` or slash command `/discuss-subtask` after `harnessed setup`.

easyinplay 93c4619 3 files · 8.9 KB Updated Sep 17, 2026

File contents

discuss-subtask workflow (v3)

Overview

1-phase sub-workflow mapping CLAUDE.md "Stage ①.c 子任务层 — superpowers brainstorming" onto harnessed runtime (Phase v3.0-3.4 W0.3 — D-04 Stage ① Discuss 三层 + D-05 phase.invokes_tools conditional fire + Pattern A sub-workflow ship)。

phase	id	upstream	model	capability / invokes_tools	gate
1	`01-brainstorm`	superpowers	opus	`{{ capabilities.superpowers-brainstorming.cmd }}` + conditional `invokes_tools[grill-with-docs, grill-me]`	`gate: judgments.subtask-gate.brainstorming.fires`

Capability refs

Sister workflows/capabilities.yaml entries:

superpowers-brainstorming — Bucket 4 (impl: superpowers, cmd: superpowers:brainstorming)
grill-with-docs — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-with-docs)
grill-me — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-me)

Gate ref

Sister workflows/judgments/subtask-gate.yaml:

brainstorming.fires — subtask.approaches >= 2 or subtask.core_algorithm == true or subtask.has_api_contract == true or subtask.error_cost == 'high'

Conditional tool invocation (D-05 invokes_tools)

phase.spec_ambiguous == true → fire grill-with-docs
phase.spec_ambiguous == true AND phase.no_docs == true → fire grill-me

Invocation

Slash command: /discuss-subtask <text> (after harnessed setup)

Routing rules

跳过条件 (sister CLAUDE.md "子任务层 ❌ 跳过"):

常规 CRUD / 跟现有模式一致
单一明显实现 (< 20 行 / 一个文件)
标准库直接调用
bug 修复且已知根因

How to invoke

Clarification needs real user dialogue, so run this stage directly in THIS session — do NOT spawn it, and do NOT improvise: follow these steps so the locked spec is persisted for the execution stages.

Evaluate the clarification criteria for "$ARGUMENTS":
- Strategic — new feature / milestone / unclear business scope → gstack /office-hours + /plan-ceo-review
- Phase — ≥2 open implementation decisions / unclear cross-phase API contract → GSD /gsd-discuss-phase
- Subtask — ≥2 distinct approaches / core algorithm / API contract design / high error cost → superpowers brainstorming
For each layer that fires, hold the dialogue with the user (use AskUserQuestion for option-style decisions) and lock every open decision.
Transparent-skip layers that don't fire — state which were skipped and why.
Persist the locked decisions to .planning/ via planning-with-files (findings.md / task_plan.md).

Output: a locked spec the execution stages (/plan → /task → /verify) consume without further user input.

References

D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)
D-05 phase.invokes_tools conditional fire (NEW v3)
workflows/capabilities.yaml — superpowers-brainstorming / grill-with-docs / grill-me
workflows/judgments/subtask-gate.yaml — brainstorming trigger
workflows/defaults.yaml — ralph_max_iterations.discuss-subtask.* values (W2.2 backfill)

---name: discuss-subtaskdescription: Stage ①.c 子任务层 discuss sub-workflow — superpowers brainstorming (≥2 approach / 核心算法 / API contract / 错误成本高)。schema_version: harnessed.workflow.v3 with disciplines_applied (6 default) + tools_available (superpowers-brainstorming + grill-with-docs + grill-me) + 1 phase (01-brainstorm with conditional invokes_tools for spec_ambiguous + no_docs)。Triggered by harnessed CLI `harnessed discuss-subtask --task <text>` or slash command `/discuss-subtask` after `harnessed setup`.---# discuss-subtask workflow (v3)## Overview1-phase sub-workflow mapping CLAUDE.md "Stage ①.c 子任务层 — superpowers brainstorming"onto harnessed runtime (Phase v3.0-3.4 W0.3 — D-04 Stage ① Discuss 三层 + D-05phase.invokes_tools conditional fire + Pattern A sub-workflow ship)。| phase | id | upstream | model | capability / invokes_tools | gate || ----- | -- | -------- | ----- | -------------------------- | ---- || 1 | `01-brainstorm` | superpowers | opus | `{{ capabilities.superpowers-brainstorming.cmd }}` + conditional `invokes_tools[grill-with-docs, grill-me]` | `gate: judgments.subtask-gate.brainstorming.fires` |## Capability refsSister `workflows/capabilities.yaml` entries:- `superpowers-brainstorming` — Bucket 4 (impl: superpowers, cmd: superpowers:brainstorming)- `grill-with-docs` — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-with-docs)- `grill-me` — Bucket 1 mattpocock (impl: mattpocock-skills, cmd: /grill-me)## Gate refSister `workflows/judgments/subtask-gate.yaml`:- `brainstorming.fires` — `subtask.approaches >= 2 or subtask.core_algorithm == true or subtask.has_api_contract == true or subtask.error_cost == 'high'`## Conditional tool invocation (D-05 invokes_tools)- `phase.spec_ambiguous == true` → fire `grill-with-docs`- `phase.spec_ambiguous == true AND phase.no_docs == true` → fire `grill-me`## Invocation- Slash command: `/discuss-subtask <text>` (after `harnessed setup`)## Routing rules跳过条件 (sister CLAUDE.md "子任务层 ❌ 跳过"):- 常规 CRUD / 跟现有模式一致- 单一明显实现 (< 20 行 / 一个文件)- 标准库直接调用- bug 修复且已知根因## How to invokeClarification needs real user dialogue, so run this stage directly in THIS session — do NOTspawn it, and do NOT improvise: follow these steps so the locked spec is persisted for theexecution stages.1. Evaluate the clarification criteria for "$ARGUMENTS": - **Strategic** — new feature / milestone / unclear business scope → gstack `/office-hours` + `/plan-ceo-review` - **Phase** — ≥2 open implementation decisions / unclear cross-phase API contract → GSD `/gsd-discuss-phase` - **Subtask** — ≥2 distinct approaches / core algorithm / API contract design / high error cost → superpowers brainstorming2. For each layer that fires, hold the dialogue with the user (use AskUserQuestion for option-style decisions) and lock every open decision.3. Transparent-skip layers that don't fire — state which were skipped and why.4. Persist the locked decisions to `.planning/` via planning-with-files (`findings.md` / `task_plan.md`).Output: a locked spec the execution stages (`/plan` → `/task` → `/verify`) consume without further user input.## References- D-04 Stage ① Discuss 三层 (战略 / phase / 子任务)- D-05 phase.invokes_tools conditional fire (NEW v3)- workflows/capabilities.yaml — superpowers-brainstorming / grill-with-docs / grill-me- workflows/judgments/subtask-gate.yaml — brainstorming trigger- workflows/defaults.yaml — ralph_max_iterations.discuss-subtask.* values (W2.2 backfill)

Frequently asked questions