feat(create-plan/codex): switch to native superpowers workflow and add guardrails

This commit is contained in:
2026-02-11 18:03:16 +00:00
parent 39d758298b
commit 76fd7f374f
4 changed files with 104 additions and 49 deletions

View File

@@ -14,6 +14,13 @@ Upon resumption, these files in this folder are the ONLY source of truth:
Do NOT reference planner-private files during implementation.
## Skill Workflow Guardrails
- Invoke relevant skills before action using native skill discovery.
- Announce which skill is being used and why.
- If a checklist-driven skill applies, track checklist execution explicitly.
- Do not use deprecated CLI wrappers for skill invocation.
---
## Quick Resume Instructions
@@ -102,17 +109,17 @@ Work from this folder (`ai_plan/YYYY-MM-DD-<short-title>/`) and always follow th
### Lint (changed files first)
```bash
# example: pnpm eslint <changed-file-1> <changed-file-2>
# example: <lint-command> <changed-file-1> <changed-file-2>
```
### Typecheck
```bash
# example: pnpm tsc --noEmit
# example: <typecheck-command>
```
### Tests (target changed scope first)
```bash
# example: pnpm test -- <related spec/file>
# example: <test-command> <related spec/file>
```
---

View File

@@ -5,6 +5,12 @@
- **Created:** YYYY-MM-DD
- **Status:** In Progress | Complete
## Planning Guardrails
- This plan assumes design was validated before implementation planning.
- Skills are invoked via native discovery (Codex: `~/.agents/skills/`).
- Deprecated CLI wrappers (for example, `superpowers-codex bootstrap` / `use-skill`) are not part of this workflow.
- Milestones require verification + local commits + explicit approval before proceeding.
## Context
### Requirements
@@ -69,17 +75,17 @@
### Types & Interfaces
```typescript
// Key type definitions
// Key type definitions (or equivalent language constructs)
```
### API Contracts
```typescript
// Endpoint signatures, request/response shapes
// Endpoint signatures, request/response shapes (if applicable)
```
### Constants & Enums
```typescript
// Shared constants
// Shared constants (if applicable)
```
## Files Inventory

View File

@@ -6,6 +6,12 @@
- **Milestones Approved:** 0/M
- **Last Updated:** YYYY-MM-DD
## Tracking Guardrails
- Update status immediately when work starts (`in-dev`) and when work completes (`completed`).
- Require explicit user approval at each milestone boundary before continuing.
- Do not push until all milestones are approved and permission is explicitly granted.
- Keep this file and `milestone-plan.md` synchronized.
---
## Milestones