Skip to content

feat: add plan status tracking to writing-plans and executing-plans #442

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Mharbulous wants to merge 1 commit into
base: main
Choose a base branch
from
+10 −3
Open

feat: add plan status tracking to writing-plans and executing-plans #442

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 4 additions & 3 deletions skills/executing-plans/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,9 +45,10 @@ Based on feedback:
### Step 5: Complete Development

After all tasks complete and verified:
- Announce: "I'm using the finishing-a-development-branch skill to complete this work."
- **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch
- Follow that skill to verify tests, present options, execute choice
1. **Mark plan as executed:** Update the plan file's YAML frontmatter from `status: pending` to `status: executed`
2. Announce: "I'm using the finishing-a-development-branch skill to complete this work."
3. **REQUIRED SUB-SKILL:** Use superpowers:finishing-a-development-branch
4. Follow that skill to verify tests, present options, execute choice

## When to Stop and Ask for Help

Expand Down
6 changes: 6 additions & 0 deletions skills/writing-plans/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,10 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
**Every plan MUST start with this header:**

```markdown
---
status: pending
---

# [Feature Name] Implementation Plan

> **For Claude:** REQUIRED SUB-SKILL: Use superpowers:executing-plans to implement this plan task-by-task.
Expand All @@ -44,6 +48,8 @@ Assume they are a skilled developer, but know almost nothing about our toolset o
---
```

**Status values:** `pending` (awaiting execution), `executed` (fully implemented). The `executing-plans` skill updates status to `executed` on completion.

## Task Structure

```markdown
Expand Down