@aayushchugh/skills 0.1.5 → 0.1.6

package/README.md

@@ -36,4 +36,5 @@ Replace `no-slop` with any id below.
 - `the-cause` — The cause. Find a bug's root cause from the report, the code path, and the evidence.
 - `go-or-stop` — Go or stop. Decide if a change is ready to ship, with a go or no-go, what to watch, and how to roll back.
 - `the-map` — The map. Map, propose, or improve a system's design like a senior engineer, grounding the recommendation in real usage and activity.
+- `whats-next` — What's next. Answer what's pending, what's next, or the status from the plan this conversation is working on.
 - `which-skill` — Which skill. Pick and run the right skill, or a chain of skills, for a request.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "@aayushchugh/skills",
-	"version": "0.1.5",
+	"version": "0.1.6",
 	"description": "The agent skills I use while building real products.",
 	"author": "Ayush Chugh <hey@ayushchugh.com>",
 	"license": "MIT",

package/skills/whats-next/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: whats-next
+description: >-
+  Use when asked what's pending, what's next, or the status of the current
+  work. Not for starting the work or changing the plan.
+---
+
+# What's next
+
+## Scope
+
+Read the plan. Do not edit it. Do not start the next todo unless asked.
+
+Answer only from the plan this conversation is implementing. Do not invent a task from memory, git, or an older plan.
+
+## Before writing
+
+Ask every blocking question in one turn. Never invent a fact. Put an unknown under Open questions and name what it blocks. Replies are 1–2 lines. Write a paragraph only when the user asks.
+
+## The plan
+
+Read the plan attached to this chat. Ignore an older plan on disk.
+
+Its todos are the only source. Each todo is `pending`, `in_progress`, or `completed`.
+
+- **What's next:** the `in_progress` todo, or the first `pending` todo when nothing is in progress. One line: that todo, and whether it has not been started or is in progress. A todo waiting on the user is not next. Say what it is waiting on.
+- **What's pending:** every todo that is not `completed`, in the plan's order.
+- **Status:** one line for done, one line for in progress, one line for still pending.
+
+When every todo is `completed`, say the plan is done. Do not pick a new task.
+
+If this conversation has no plan, say so.
+
+## Replies
+
+Name the plan. Answer only the question asked. "What's next" is one todo. "What's pending" is the open list. "Status" is the three lines. Do not dump the whole plan.

package/skills/which-skill/SKILL.md

@@ -30,6 +30,7 @@ Read the chosen skill and follow it. Do not restate its rules here.
 | Diagnose or debug a failure | `the-cause` |
 | Release check or go / no-go | `go-or-stop` |
 | System design, architecture review, or scale/performance improvement | `the-map` |
+| What's pending, what's next, or the status of the current plan | `whats-next` |
 
 Run one skill when one fits. Say which skill or chain you picked in one line. Ask one question when two skills fit equally.