Feature/enhancing ai user story creator (#92)

* feat: enhance AI user story generation with optional context and improved output structure

* feat: add integration guide and workflow tips for user story generation

* fix: remove unnecessary validateInput property from context input prompt

* feat: implement UserStoryPromptService for user story generation

- Added UserStoryPromptService to manage user story generation prompts.
- Refactored prompt building logic into UserStoryPromptService.
- Created unit tests for UserStoryPromptService covering prompt generation and validation.
- Updated tsconfig.json to include test files in the compilation.

* test: add unit tests for UserStoryPromptService functionality

---------

Co-authored-by: Jason Rueckert <[email protected]>

Author: jsonify

README.md

@@ -1,6 +1,6 @@
 # Noted - Your Personal Knowledge Base in VS Code
 
-> **💖 Love Noted? Help us grow!** This extension is built and maintained by the community. If you find Noted useful, please [**rate and review it on the VS Code Marketplace**](https://marketplace.visualstudio.com/items?itemName=jsonify.noted&ssr=false#review-details) — your feedback helps others discover Noted and motivates us to keep improving. Every star counts! ⭐
+> **💖 Love Noted? Help us grow!** This extension is built and maintained by the community. If you find Noted useful, please [**rate and review it on the VS Code Marketplace**](https://marketplace.visualstudio.com/items?itemName=jsonify.noted&ssr=false#review-details) — your feedback helps others discover Noted and motivates us to keep improving. Every star counts!
 
 ---
 [Repository](https://github.com/jsonify/noted)  |  [Issues](https://github.com/jsonify/noted/issues)  |  [Documentation](https://jsonify.github.io/noted/)

docs/_posts/2025-10-24-templates.md

@@ -362,11 +362,287 @@ function example() {
 ```
 ````
 
+## AI-Powered User Story Generation
+
+**Generate comprehensive, technical user stories** with AI assistance for agile software development.
+
+### Quick Start
+
+1. Open Command Palette (`Cmd+Shift+P`)
+2. Run "Noted: Create User Story with AI"
+3. Enter brief description (e.g., "Set up GCP project with networking")
+4. Choose whether you have additional context
+5. (Optional) Paste architecture details, dependencies, tech stack
+6. Review and create!
+
+### What You Get
+
+The AI generates a **production-ready user story** with:
+
+- **Scope Statement**: What part of the system this addresses
+- **Story Title**: Concise, specific title
+- **Description**: Professional "As a [role], I want [goal], So that [benefit]" format
+- **5-15 Technical Tasks**: Specific, actionable steps with service names
+- **3-7 Acceptance Criteria**: Testable, verifiable outcomes
+- **Dependencies**: Required access, prerequisites, blocking items
+- **Time Estimate**: Realistic effort estimation
+
+### Example Output
+
+**Input**:
+```
+Description: Establish GCP project and core networking infrastructure
+Context: Integration with JFrog Cloud, VPN to on-prem AD, uses Cloud NAT,
+DataProc, GKE, GAR, requires network peering with JFrog-managed services
+```
+
+**Generated User Story**:
+
+```markdown
+---
+tags: [user-story]
+created: 2025-11-13T22:30:26.883Z
+status: draft
+---
+
+# User Story: Establish GCP Project and Core Networking Infrastructure
+
+**Created:** Thursday, November 13, 2025 | **Author:** jruecke
+
+## Scope
+Foundation for the Managed GCP section of multi-cloud deployment
+
+## Story Title
+Establish GCP Project and Core Networking Infrastructure
+
+## Description
+As a Platform Engineer,
+I want a properly configured GCP project with networking for JFrog SaaS,
+So that development teams have secure infrastructure for deploying services.
+
+### Tasks
+- [ ] Create GCP project(s) with appropriate billing and IAM structure
+- [ ] Configure VPC networks for GCP region deployment
+- [ ] Establish subnet allocation for Cloud Run, DataProc, GKE, and GAR
+- [ ] Configure Cloud NAT and Cloud Router
+- [ ] Set up VPC firewall rules for inter-service communication
+- [ ] Configure private Google access for subnets
+- [ ] Establish connectivity to JFrog Cloud Global Load Balancer
+- [ ] Establish VPN/Interconnect to on-premises for authentication
+- [ ] Set up VPC peering requirements for JFrog-managed services
+- [ ] Document network architecture diagram
+- [ ] Set up initial Cloud Logging and Cloud Monitoring workspace
+
+## Acceptance Criteria
+- [ ] GCP project provisioned and accessible
+- [ ] VPC networks configured with connectivity to JFrog Cloud
+- [ ] Network connectivity to authentication provider verified
+- [ ] Firewall rules allow traffic flow per architecture
+- [ ] Architecture documentation created
+
+## Dependencies
+- JFrog SaaS subscription and architecture guidance
+- Authentication provider details (LDAP/AD endpoints)
+- Network IP addressing scheme approved
+
+## Estimate
+**Time to Complete:** 2-3 days
+```
+
+### Pro Tips for Better Results
+
+**1. Be Specific**: Instead of "Add user authentication", say "Add OAuth2 authentication with Google Sign-In"
+
+**2. Provide Context**: Include:
+   - Integration points (APIs, services, external systems)
+   - Technology stack (languages, frameworks, cloud services)
+   - Dependencies (what must exist first)
+   - Architecture constraints (security, compliance, scalability)
+
+**3. Example Context Formats**:
+
+```
+# Infrastructure Story
+Context: Uses AWS EKS, RDS PostgreSQL, ALB, integrates with
+DataDog monitoring, requires IAM roles for service accounts
+
+# Feature Story
+Context: React frontend, Node.js backend, MongoDB, uses Stripe API,
+needs WebSocket for real-time updates
+
+# Integration Story
+Context: Connects to Salesforce API v52, uses OAuth2, requires
+scheduled sync every 15 minutes, max 10k records per sync
+```
+
+**4. Without Context**: Still works! AI generates good generic stories, just less specific to your architecture
+
+### How It Works
+
+1. **Query Analysis**: AI analyzes your description and context
+2. **Technical Depth**: Generates 5-15 tasks based on complexity
+   - Simple features: 5-7 tasks
+   - Complex infrastructure: 8-12+ tasks
+3. **Specific Details**: Incorporates service names, tech stack from context
+4. **Professional Format**: Follows agile best practices
+5. **Saved**: Note created in `Notes/User Stories/` folder
+
+### Configuration
+
+Uses your preferred AI model (Claude Sonnet, GPT-4, etc.):
+
+```
+Setting: noted.templates.preferredModel
+Default: Automatic (Claude > GPT > Gemini)
+```
+
+### Best Practices
+
+**DO**:
+- ✅ Include specific technologies and services in context
+- ✅ Mention integration points between systems
+- ✅ Specify compliance or security requirements
+- ✅ List blocking dependencies upfront
+
+**DON'T**:
+- ❌ Use vague descriptions like "make it better"
+- ❌ Skip context for complex infrastructure tasks
+- ❌ Forget to mention external systems or APIs
+- ❌ Ignore prerequisites or access requirements
+
+### Comparison: With vs Without Context
+
+| Without Context | With Context |
+|----------------|--------------|
+| "Create a new GCP project" | "Create GCP project with billing, enable Compute Engine, Cloud Storage, and Kubernetes Engine APIs" |
+| "Set up networking" | "Configure VPC with subnets for dev/prod, Cloud NAT, Cloud Router, firewall rules for SSH/HTTPS from specific IPs" |
+| "Configure access" | "Set up IAM roles for Project Admin and Developer, configure VPN to on-prem AD for authentication" |
+
+**Result**: Context gives you 3x more actionable, technical detail!
+
+### Integration Guide
+
+**How generated stories work with existing tag/link systems**
+
+User stories integrate seamlessly with Noted's existing features:
+
+**Tags System**:
+- Generated stories automatically include `[user-story]` tag in frontmatter
+- Stories are tagged with `status: draft` by default
+- Use tag autocomplete to add custom tags: `#feature`, `#infrastructure`, `#bug-fix`
+- Find all stories: Use Tags view → filter by `user-story`
+- Rename/merge tags: Right-click any tag → Rename Tag (affects all stories)
+
+**Wiki Links**:
+- Add `[[dependencies]]` to link prerequisite stories or notes
+- Reference design docs: `[[architecture-diagram]]`, `[[api-spec]]`
+- Link to related stories: `[[user-story-authentication]]`
+- Backlinks panel automatically shows which stories reference this one
+- Graph view visualizes story dependencies
+
+**Smart Collections**:
+- Filter stories by status: Create collection with `status: draft`
+- Group by priority: Use `priority: high` in frontmatter
+- Track sprint stories: Add `sprint: 2025-11` tag
+
+**Example Integration**:
+```markdown
+---
+tags: [user-story, infrastructure, gcp]
+created: 2025-11-13T22:30:26.883Z
+status: in-progress
+priority: high
+sprint: 2025-12
+---
+
+# User Story: Establish GCP Project
+
+## Dependencies
+- [[network-design-doc]] - IP addressing scheme
+- [[security-requirements]] - Firewall rules
+- [[jfrog-integration-guide]] - VPC peering setup
+
+## Related Stories
+- [[user-story-gke-cluster]] - Depends on this networking
+- [[user-story-monitoring]] - Uses same GCP project
+
+Tags: #gcp #networking #infrastructure
+```
+
+**Workflow Tips**:
+- Create story → Add wiki links → View graph → See dependencies
+- Tag stories by epic: `#epic-authentication`, `#epic-infrastructure`
+- Use Connections panel to track which stories reference this one
+- Archive completed stories to keep workspace clean
+
+### FAQ
+
+**Q: When should I provide context?**
+
+A: Provide context when:
+- ✅ **Complex infrastructure**: Cloud setup, networking, security configs
+- ✅ **Integrations**: Connecting to external APIs or services
+- ✅ **Specific tech stack**: Using particular frameworks, languages, or tools
+- ✅ **Architecture constraints**: Security, compliance, scalability requirements
+- ✅ **Multiple systems**: Stories spanning databases, backends, frontends
+
+Skip context when:
+- ❌ Simple features: "Add a logout button" (description alone is enough)
+- ❌ Obvious tech: "Fix typo in docs" (no technical depth needed)
+- ❌ UI-only changes: "Change button color to blue"
+
+**Rule of thumb**: If you'd need to explain your architecture to a new team member, provide that as context!
+
+---
+
+**Q: Can I edit the generated story?**
+
+A: **Yes, absolutely!** Generated stories are standard notes—edit freely:
+
+**How to edit**:
+1. Click the generated story in Notes tree view
+2. Edit directly in VS Code editor
+3. Changes auto-save like any note
+
+**What to edit**:
+- ✏️ **Tasks**: Add/remove/reorder checklist items
+- ✏️ **Acceptance Criteria**: Make criteria more/less specific
+- ✏️ **Description**: Refine the "As a... I want... So that..." statement
+- ✏️ **Estimate**: Adjust time based on team velocity
+- ✏️ **Dependencies**: Add forgotten prerequisites
+- ✏️ **Tags**: Add custom tags like `#sprint-12`, `#team-backend`
+- ✏️ **Links**: Add wiki links to related notes: `[[design-doc]]`
+
+**Pro tips**:
+- Use AI output as a **starting point**, not final draft
+- Break large stories into smaller ones (copy/paste tasks)
+- Add team-specific details AI couldn't know
+- Update tasks as you complete them: `- [x] Completed task`
+- Add notes/findings under tasks during implementation
+
+**Example edit**:
+```markdown
+### Tasks (AI Generated)
+- [ ] Configure VPC networks for GCP region deployment
+- [ ] Set up VPC firewall rules for inter-service communication
+
+### Tasks (After Editing)
+- [x] Configure VPC networks for GCP region deployment
+  - Note: Used CIDR 10.0.0.0/16 for dev, 10.1.0.0/16 for prod
+- [ ] Set up VPC firewall rules for inter-service communication
+  - Added: Allow SSH from bastion host (10.0.1.0/24)
+  - Added: Allow HTTPS from ALB subnet
+  - See: [[firewall-rules-doc]] for full config
+```
+
+**Remember**: AI gives you ~80% of the story—you add the final 20% that makes it perfect for your team!
+
 ## Related Features
 
 - [Daily Notes](/noted/posts/daily-notes/) - Quick daily note access
 - [Tags](/noted/posts/tags/) - Organize with tags
 - [Wiki Links](/noted/posts/wiki-links/) - Connect notes
+- [Bundles](/noted/posts/bundles/) - Multi-note workflows
 
 ---
 

notes.md

@@ -784,6 +784,30 @@ pnpm run test
 
 ## Recent Updates
 
+### Enhanced User Story Generation (v1.41.3 - 2025-11-13)
+- **Optional Context Collection**: Prompt to add architecture details, dependencies, tech stack
+  - Two-step input: Brief description + optional detailed context
+  - Context significantly improves technical specificity
+  - Examples provided for infrastructure, feature, and integration stories
+- **Improved AI Prompts**: Enhanced to generate comprehensive, technical user stories
+  - Requests 5-15 tasks based on complexity (vs previous 3-5)
+  - Emphasizes specific service names, integration points, technical details
+  - Instructions differentiate simple features (5-7 tasks) from complex infrastructure (8-12+ tasks)
+  - Guides AI to include configuration details and actionable steps
+- **Extended Data Model**: New fields in user story structure
+  - **Scope**: What part of the system/architecture this story addresses
+  - **Dependencies**: List of prerequisites, access requirements, blocking items
+  - Both fields fully integrated into generation and note templates
+- **Enhanced Note Template**: Richer output format
+  - Scope section clearly defines boundaries
+  - Dependencies section lists blocking requirements
+  - Supports empty dependencies with "- None" fallback
+- **Better Results**: Matches quality of web-based Claude interactions
+  - Technical depth comparable to manual story writing
+  - Specific service names and tools referenced in tasks
+  - Architecture-aware acceptance criteria
+  - Realistic dependencies based on context
+
 ### AI Summarization Phase 4 (v1.39.0 - 2025-11-07)
 - **Custom Prompt Templates**: Create and use custom prompts for AI summarization
   - Built-in templates: Default, Technical Deep Dive, Meeting Summary, Code Review, Brainstorm