v1.0.3

.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`

.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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase:
 

.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`

.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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase:
 

.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`

.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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase:
 

.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`

.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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase:
 

.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`

.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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase:
 

.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`

.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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase:
 

.gitignore

@@ -0,0 +1,2 @@
+specs/
+video-promo/

.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`

.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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase:
 

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/<feature-name>/` 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

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`

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/<feature-name>` 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/<feature-name>/overview.md` - To see overall progress and identify the next phase
+> specs feature folder
-2. `specs/<feature-name>/Phase X.md` - The specific phase to implement
+>
+> - `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 feature folder
-> - `specs/user-auth/Phase 3.md`"
+>
+> - `specs/user-authentication/`
+>
+> OR
+>
+> specs overview and phase files
+>
+> - `specs/user-authentication/overview.md`
+> - `specs/user-authentication/Phase 3.md`"
 
 Example for final phase: