diff --git a/.agent/workflows/plan2code-2--document.md b/.agent/workflows/plan2code-2--document.md index 51f615a..1d285cb 100644 --- a/.agent/workflows/plan2code-2--document.md +++ b/.agent/workflows/plan2code-2--document.md @@ -286,7 +286,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/.agent/workflows/plan2code-3--implement.md b/.agent/workflows/plan2code-3--implement.md index fc0902a..d331221 100644 --- a/.agent/workflows/plan2code-3--implement.md +++ b/.agent/workflows/plan2code-3--implement.md @@ -17,10 +17,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -240,8 +248,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: diff --git a/.claude/commands/plan2code-2--document.md b/.claude/commands/plan2code-2--document.md index a81090e..2bfaeb6 100644 --- a/.claude/commands/plan2code-2--document.md +++ b/.claude/commands/plan2code-2--document.md @@ -282,7 +282,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/.claude/commands/plan2code-3--implement.md b/.claude/commands/plan2code-3--implement.md index 575bb16..491193a 100644 --- a/.claude/commands/plan2code-3--implement.md +++ b/.claude/commands/plan2code-3--implement.md @@ -13,10 +13,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -236,8 +244,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: diff --git a/.continue/prompts/plan2code-2--document.prompt.md b/.continue/prompts/plan2code-2--document.prompt.md index f9e168a..72e6a88 100644 --- a/.continue/prompts/plan2code-2--document.prompt.md +++ b/.continue/prompts/plan2code-2--document.prompt.md @@ -287,7 +287,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/.continue/prompts/plan2code-3--implement.prompt.md b/.continue/prompts/plan2code-3--implement.prompt.md index 4ca239f..f41fc4b 100644 --- a/.continue/prompts/plan2code-3--implement.prompt.md +++ b/.continue/prompts/plan2code-3--implement.prompt.md @@ -18,10 +18,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -241,8 +249,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: diff --git a/.cursor/rules/plan2code-2--document.mdc b/.cursor/rules/plan2code-2--document.mdc index 3151ccb..bce8f1a 100644 --- a/.cursor/rules/plan2code-2--document.mdc +++ b/.cursor/rules/plan2code-2--document.mdc @@ -287,7 +287,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/.cursor/rules/plan2code-3--implement.mdc b/.cursor/rules/plan2code-3--implement.mdc index 154b442..8246091 100644 --- a/.cursor/rules/plan2code-3--implement.mdc +++ b/.cursor/rules/plan2code-3--implement.mdc @@ -18,10 +18,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -241,8 +249,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: diff --git a/.github/agents/plan2code-2--document.agent.md b/.github/agents/plan2code-2--document.agent.md index 51f615a..1d285cb 100644 --- a/.github/agents/plan2code-2--document.agent.md +++ b/.github/agents/plan2code-2--document.agent.md @@ -286,7 +286,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/.github/agents/plan2code-3--implement.agent.md b/.github/agents/plan2code-3--implement.agent.md index fc0902a..d331221 100644 --- a/.github/agents/plan2code-3--implement.agent.md +++ b/.github/agents/plan2code-3--implement.agent.md @@ -17,10 +17,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -240,8 +248,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: diff --git a/.github/prompts/plan2code-2--document.prompt.md b/.github/prompts/plan2code-2--document.prompt.md index 6c58278..a4da546 100644 --- a/.github/prompts/plan2code-2--document.prompt.md +++ b/.github/prompts/plan2code-2--document.prompt.md @@ -287,7 +287,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/.github/prompts/plan2code-3--implement.prompt.md b/.github/prompts/plan2code-3--implement.prompt.md index ccc2756..a53aed6 100644 --- a/.github/prompts/plan2code-3--implement.prompt.md +++ b/.github/prompts/plan2code-3--implement.prompt.md @@ -18,10 +18,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -241,8 +249,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..3eee8b0 --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +specs/ +video-promo/ \ No newline at end of file diff --git a/.windsurf/workflows/plan2code-2--document.md b/.windsurf/workflows/plan2code-2--document.md index 51f615a..1d285cb 100644 --- a/.windsurf/workflows/plan2code-2--document.md +++ b/.windsurf/workflows/plan2code-2--document.md @@ -286,7 +286,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/.windsurf/workflows/plan2code-3--implement.md b/.windsurf/workflows/plan2code-3--implement.md index fc0902a..d331221 100644 --- a/.windsurf/workflows/plan2code-3--implement.md +++ b/.windsurf/workflows/plan2code-3--implement.md @@ -17,10 +17,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -240,8 +248,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: diff --git a/CHANGELOG.md b/CHANGELOG.md index 5d9b49a..ef2232d 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,6 +2,13 @@ All notable changes to Plan2Code will be documented in this file. +## v1.0.3 - 2025-12-05 + +### 📦 Updated + +- Improved spec file referencing in Documentation and Implementation modes - users can now reference either a `specs//` folder or individual files +- Implementation mode now auto-detects single spec folders before prompting the user for file references + ## v1.0.2 - 2025-12-05 ### 🐛 Fixed diff --git a/plan2code-2--document.md b/plan2code-2--document.md index a81090e..2bfaeb6 100644 --- a/plan2code-2--document.md +++ b/plan2code-2--document.md @@ -282,7 +282,15 @@ Example closing: > "Documentation complete. Implementation specs are in `specs/user-authentication/`. > -> **Next step:** In a NEW conversation, use the implement command and attach: +> **Next step:** In a NEW conversation, use the implement command and attach/reference: +> +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files > > - `specs/user-authentication/overview.md` > - `specs/user-authentication/Phase 1.md` diff --git a/plan2code-3--implement.md b/plan2code-3--implement.md index 575bb16..491193a 100644 --- a/plan2code-3--implement.md +++ b/plan2code-3--implement.md @@ -13,10 +13,18 @@ You are a senior software engineer with extensive experience building scalable, ## Required Context -You need the implementation spec files to proceed. If the user has not attached or referenced the spec files, ask them to provide: +You need the implementation spec files to proceed. First look for a single `specs/` folder if the user has not attached or referenced the spec files. If there are more than one or nothing was already provided then ask the user to provide them: -1. `specs//overview.md` - To see overall progress and identify the next phase -2. `specs//Phase X.md` - The specific phase to implement +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 1.md` **Do not proceed until you have BOTH files.** @@ -236,8 +244,16 @@ Example for continuing: > "Phase 2 complete. In a NEW conversation, use the implement command and attach: > -> - `specs/user-auth/overview.md` -> - `specs/user-auth/Phase 3.md`" +> specs feature folder +> +> - `specs/user-authentication/` +> +> OR +> +> specs overview and phase files +> +> - `specs/user-authentication/overview.md` +> - `specs/user-authentication/Phase 3.md`" Example for final phase: