gsd-vscode-copilot 1.0.0 → 1.1.0

package/templates/prompts/gsd-execute-plan.prompt.md

@@ -1,96 +0,0 @@
----
-description: "GSD: Execute a plan file (run verify, stop on checkpoints)"
-argument-hint: "Provide the plan path (e.g., .planning/phases/03-auth/03-01-PLAN.md)"
-agent: agent
----
-
-Execute a GSD-style plan file.
-
-## Instructions
-
-1. If no plan path provided, ask which PLAN file to execute.
-2. Read the PLAN file — it IS the executable prompt.
-3. Execute tasks sequentially.
-
-## For each task
-
-### `type="auto"` tasks
-
-1. Implement the changes described in `<action>`
-2. Run the `<verify>` command(s)
-3. If verification fails: stop and report the failure with proposed fixes
-4. If verification passes: confirm `<done>` criteria met and continue
-
-### `type="checkpoint:*"` tasks
-
-1. **STOP immediately** (do not continue to next task)
-2. Display a clear checkpoint message:
-
-```
-════════════════════════════════════════
-CHECKPOINT: [Type]
-════════════════════════════════════════
-
-Task [X] of [Y]: [Task name]
-
-[For human-verify]: What was built, how to verify
-[For decision]: Options with pros/cons
-
-Resume signal: [How to continue]
-════════════════════════════════════════
-```
-
-3. Wait for my response before continuing
-
-## After all tasks complete
-
-1. Run the overall `<verification>` checks from the plan
-2. Confirm all `<success_criteria>` are met
-3. Create the SUMMARY file as specified in `<output>`
-
-### SUMMARY format
-
-Create `.planning/phases/NN-name/NN-PP-SUMMARY.md`:
-
-```markdown
-# Phase [X] Plan [Y]: [Name] Summary
-
-**[One-liner describing what was accomplished]**
-
-## Accomplishments
-- [What was built]
-
-## Files Created/Modified
-- `path/to/file` - What it does
-
-## Decisions Made
-[Key decisions, or "None - followed plan as specified"]
-
-## Issues Encountered
-[Problems and resolutions, or "None"]
-
-## Next Phase Readiness
-[What's ready for next phase]
-```
-
-4. Update `.planning/STATE.md` with:
-   - Current position
-   - Any decisions made
-   - Next action
-
-## Git commits
-
-After verification passes, offer to create a commit:
-- Show `git status` summary
-- Propose a commit message following: `feat(NN-PP): [description]`
-- Ask for explicit confirmation before committing
-
-**Never commit without explicit "yes" from the user.**
-
-## Output
-
-Report:
-- Tasks completed
-- Verification results
-- Summary path
-- Any follow-ups or risks discovered

package/templates/prompts/gsd-plan-slice.prompt.md

@@ -1,105 +0,0 @@
----
-description: "GSD: Plan a small executable slice (2–3 tasks)"
-argument-hint: "What slice are we planning? (e.g., 'Phase 03: User authentication')"
-agent: agent
----
-
-Plan the next small slice of work as a **GSD-style phase plan** (2–3 tasks max).
-
-## Context to load
-
-- Read `.planning/STATE.md` and `.planning/ROADMAP.md`.
-- Identify the current phase directory under `.planning/phases/` (or ask me which phase).
-- If a feature is mentioned, locate the relevant code and reference the specific files to be changed.
-
-## Plan file location
-
-Create a new plan file under:
-- `.planning/phases/<NN-name>/` (create the directory if missing)
-
-Name the file:
-- `<NN>-<PP>-PLAN.md` (example: `03-01-PLAN.md` for Phase 3, Plan 1)
-
-## Plan format
-
-Follow the template in `.github/vendor/get-shit-done/templates/phase-prompt.md`.
-
-### Required structure
-
-```markdown
----
-phase: NN-name
-plan: PP
-type: execute
-wave: 1
-depends_on: []
-files_modified: []
-autonomous: true
----
-
-<objective>
-[What this plan accomplishes]
-
-Purpose: [Why this matters]
-Output: [What artifacts will be created]
-</objective>
-
-<context>
-@.planning/PROJECT.md
-@.planning/ROADMAP.md
-@.planning/STATE.md
-[Relevant source files]
-</context>
-
-<tasks>
-
-<task type="auto">
-  <name>Task 1: [Action-oriented name]</name>
-  <files>path/to/file.ext</files>
-  <action>[Specific implementation - what to do, how to do it, what to avoid and WHY]</action>
-  <verify>[Command or check to prove it worked]</verify>
-  <done>[Measurable acceptance criteria]</done>
-</task>
-
-<!-- Repeat for 2-3 tasks total -->
-
-</tasks>
-
-<verification>
-Before declaring plan complete:
-- [ ] [Specific test/build command]
-- [ ] [Behavior verification]
-</verification>
-
-<success_criteria>
-- All tasks completed
-- All verification checks pass
-- [Plan-specific criteria]
-</success_criteria>
-
-<output>
-After completion, create `.planning/phases/NN-name/NN-PP-SUMMARY.md`
-</output>
-```
-
-## Task types
-
-| Type | Use for |
-|------|---------|
-| `auto` | Everything that can be done autonomously |
-| `checkpoint:human-verify` | Visual/functional verification needed |
-| `checkpoint:decision` | Implementation choice needed |
-
-## Guidelines
-
-- **2–3 tasks max** per plan
-- Each task must have: `<files>`, `<action>`, `<verify>`, `<done>`
-- `<verify>` should use actual commands for your stack (e.g., `npm test`, `dotnet build`)
-- Prefer vertical slices (model + API + UI) over horizontal layers
-
-## Output
-
-Write the plan file, then reply with:
-- Plan path
-- Summary of what will be built
-- Any open questions that block execution