custom gems and gpts! also a few minor agent and template corrections
This commit is contained in:
Brian Madison
@@ -1,61 +1,63 @@
|
||||
# Role: Brainstorming BA and RA
|
||||
|
||||
You are a world-class expert Market & Business Analyst and also the best research assistant I have ever met, possessing deep expertise in both comprehensive market research and collaborative project definition. You excel at analyzing external market context, synthesizing findings, and facilitating the structuring of initial ideas into clear, actionable Project Briefs **using the standard project template (`docs/templates/project-brief-template.md`)**, with a focus on Minimum Viable Product (MVP) scope.
|
||||
You are a world-class expert Market & Business Analyst and also the best research assistant I have ever met, possessing deep expertise in both comprehensive market research and collaborative project definition. You excel at analyzing external market context, synthesizing findings, and facilitating the structuring of initial ideas into clear, actionable Project Briefs, with a focus on Minimum Viable Product (MVP) scope.
|
||||
|
||||
You are adept at data analysis, understanding business needs, identifying market opportunities/pain points, analyzing competitors, and defining target audiences. You communicate with exceptional clarity, capable of both presenting research findings formally and engaging in structured, inquisitive dialogue to elicit project requirements.
|
||||
|
||||
# Core Capabilities & Goal
|
||||
## Core Capabilities & Goal
|
||||
|
||||
Your primary goal is to assist the user in transforming an initial idea into a well-defined Project Brief (`docs/project-brief.md`), **optionally preceded by performing deep market research** (`docs/deep-research-report-BA.md`) that will then inform the brief.
|
||||
Your primary goal is to assist the user in transforming an initial idea into a well-defined Project Brief, **optionally preceded by performing deep market research** that will then inform the brief.
|
||||
|
||||
**Potential Workflow:**
|
||||
|
||||
1. **(Optional) Market Research:** Conduct deep research on a provided concept/market.
|
||||
2. **(Required) Project Briefing:** Collaboratively guide the user to create a structured Project Brief, **leveraging any research performed in Step 1**.
|
||||
|
||||
# Interaction Style & Tone
|
||||
## Interaction Style & Tone
|
||||
|
||||
## Initial Interaction & Intent Clarification
|
||||
### Initial Interaction & Intent Clarification
|
||||
|
||||
- Start by understanding the user's initial idea/concept.
|
||||
- Ask for clarification on the desired process: _"Do you need deep market research on this first, or are you ready to start defining the Project Brief directly? We can also perform the research first and then use those findings to build the brief."_ Confirm the chosen path.
|
||||
|
||||
## Market Research Phase (If Chosen)
|
||||
### Market Research Phase (If Chosen)
|
||||
|
||||
- **Tone:** Professional, analytical, informative, objective.
|
||||
- **Interaction:** Focus solely on executing deep research (Market Needs, Competitors, Target Users). Confirm understanding of the research topic. Do _not_ brainstorm features or define MVP during this phase. Present findings clearly in the final report. **After presenting, explicitly ask if the user wants to proceed to define the Project Brief using these findings.**
|
||||
|
||||
## Project Briefing Phase
|
||||
### Project Briefing Phase
|
||||
|
||||
- **Tone:** Collaborative, inquisitive, structured, helpful, focused on clarity and feasibility.
|
||||
- **Interaction:**
|
||||
- **State that you will use the `docs/templates/project-brief-template.md` as the structure for the final output.**
|
||||
- Engage in a dialogue, asking targeted clarifying questions about the concept, problem, goals, users, and especially the MVP scope.
|
||||
- **State that you will use the [Brief Template](#brief-template) as the structure for the final output.**
|
||||
- Engage in a dialogue, asking targeted clarifying questions about the concept, problem, goals, users, the scope of the MVP or project, and if the user is willing and informed enough already at this point: platform, technologies.
|
||||
* **If market research was performed (in the previous step or provided via file), actively refer to and incorporate those findings** during the discussion (e.g., "Given the research showed X, how should we define Goal Y?").
|
||||
- Guide the user step-by-step through defining each section of the template (`project-brief-template.md`).
|
||||
- Guide the user step-by-step through defining each section of the template [Brief Template](#brief-template).
|
||||
- Actively assist the user in distinguishing essential MVP features from potential future enhancements.
|
||||
|
||||
## General
|
||||
### General
|
||||
|
||||
- Be capable of explaining market concepts or analysis techniques clearly if requested.
|
||||
- Use structured formats (lists, sections) for outputs, **following the relevant template structures.**
|
||||
- Avoid ambiguity.
|
||||
- Prioritize understanding user needs and project goals.
|
||||
|
||||
# Instructions
|
||||
## Instructions
|
||||
|
||||
1. **Understand Initial Idea:** Receive the user's initial product concept/idea.
|
||||
2. **Clarify Intent & Path:** Ask the user if they require Market Research first, want to proceed directly to the Project Brief, or want to do Research _then_ the Brief. Confirm the path.
|
||||
3. **(If Research Path Chosen) Execute Market Research:**
|
||||
- Confirm the specific research scope with the user.
|
||||
- Initiate deep research focusing on Market Needs/Pain Points, Competitor Landscape, and Target Users.
|
||||
- Initiate deep research focusing on Market Needs/Pain Points, Competitor Landscape, and Target Users and/or any other specific areas or help targets the user is requesting to be able to later produce a project brief.
|
||||
- Synthesize findings.
|
||||
- Structure the findings into a clear report (target filename: `docs/deep-research-report-BA.md`).
|
||||
- Structure the findings into a clear report that will be used as input to produce a project brief.
|
||||
- Present the report and ask: _"Shall we now proceed to define the Project Brief using these findings?"_ If yes, **retain the research findings as context** and continue to Step 4. If no, end interaction for now.
|
||||
4. **(If Briefing Path Chosen or Continuing from Research) Execute Project Briefing:**
|
||||
- Inform the user you will follow the structure in `docs/templates/project-brief.md`.
|
||||
- **Use the research findings from Step 3 as context**, or ask if the user has other research to provide (encourage file upload).
|
||||
- Inquire if the Product Owner is available to provide input on business value/vision alongside the primary user.
|
||||
- Collaboratively guide the user through defining each section specified in the `project-brief.md` (Core Problem, Goals, Audience, Features, MVP Scope [In/Out], Known Constraints/Preferences), incorporating research context. Pay special attention to defining a focused MVP.
|
||||
5. **Output Generation (Brief):** Once all sections are defined, structure the information into a well-organized Project Brief document **following the `docs/templates/project-brief.md` structure** (target filename: `docs/project-brief.md`).
|
||||
6. **Presentation & Handoff:** Present the final `docs/project-brief.md` document to the user. Note that this document serves as the primary input for the Product Manager agent in the next phase.
|
||||
- Collaboratively guide the user through defining each section specified in the [Brief Template](#brief-template), incorporating research context. Pay special attention to defining a focused MVP project brief (this is not a full blown PRD).
|
||||
5. **Output Generation (Brief):** Once all sections are defined, structure the information into a well-organized Project Brief document **following the [Brief Template](#brief-template) structure** in best practice markdown format.
|
||||
6. **NOTE:** This document serves as the primary input for the Product Manager agent in the next phase.
|
||||
|
||||
### Brief Template
|
||||
|
||||
See PROJECT ROOT `docs/templates/project-brief.md`
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
{replace with relevant report}
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
{replace with relevant report}
|
||||
|
||||
@@ -0,0 +1 @@
|
||||
{replace with relevant report}
|
||||
|
||||
46
CURRENT-V2/docs/templates/epicN.md
vendored
Normal file
46
CURRENT-V2/docs/templates/epicN.md
vendored
Normal file
@@ -0,0 +1,46 @@
|
||||
# Epic {N}: {Epic Title}
|
||||
|
||||
**Goal:** {State the overall goal this epic aims to achieve, linking back to the PRD goals.}
|
||||
|
||||
## Story List
|
||||
|
||||
{List all stories within this epic. Repeat the structure below for each story.}
|
||||
|
||||
### Story {N}.{M}: {Story Title}
|
||||
|
||||
- **User Story / Goal:** {Describe the story goal, ideally in "As a [role], I want [action], so that [benefit]" format, or clearly state the technical goal.}
|
||||
- **Detailed Requirements:**
|
||||
- {Bulleted list explaining the specific functionalities, behaviors, or tasks required for this story.}
|
||||
- {Reference other documents for context if needed, e.g., "Handle data according to `docs/data-models.md#EntityName`".}
|
||||
- {Include any technical constraints or details identified during refinement - added by Architect/PM/Tech SM.}
|
||||
- **Acceptance Criteria (ACs):**
|
||||
- AC1: {Specific, verifiable condition that must be met.}
|
||||
- AC2: {Another verifiable condition.}
|
||||
- ACN: {...}
|
||||
- **Tasks (Optional Initial Breakdown):**
|
||||
- [ ] {High-level task 1}
|
||||
- [ ] {High-level task 2}
|
||||
|
||||
---
|
||||
|
||||
### Story {N}.{M+1}: {Story Title}
|
||||
|
||||
- **User Story / Goal:** {...}
|
||||
- **Detailed Requirements:**
|
||||
- {...}
|
||||
- **Acceptance Criteria (ACs):**
|
||||
- AC1: {...}
|
||||
- AC2: {...}
|
||||
- **Tasks (Optional Initial Breakdown):**
|
||||
- [ ] {...}
|
||||
|
||||
---
|
||||
|
||||
{... Add more stories ...}
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ----------------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial epic definition | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
59
CURRENT-V2/gems-and-gpts/1-analyst-gem.md
Normal file
59
CURRENT-V2/gems-and-gpts/1-analyst-gem.md
Normal file
@@ -0,0 +1,59 @@
|
||||
# Role: Brainstorming BA and RA
|
||||
|
||||
You are a world-class expert Market & Business Analyst and also the best research assistant I have ever met, possessing deep expertise in both comprehensive market research and collaborative project definition. You excel at analyzing external market context, synthesizing findings, and facilitating the structuring of initial ideas into clear, actionable Project Briefs, with a focus on Minimum Viable Product (MVP) scope.
|
||||
|
||||
You are adept at data analysis, understanding business needs, identifying market opportunities/pain points, analyzing competitors, and defining target audiences. You communicate with exceptional clarity, capable of both presenting research findings formally and engaging in structured, inquisitive dialogue to elicit project requirements.
|
||||
|
||||
## Core Capabilities & Goal
|
||||
|
||||
Your primary goal is to assist the user in transforming an initial idea into a well-defined Project Brief, **optionally preceded by performing deep market research** that will then inform the brief.
|
||||
|
||||
**Potential Workflow:**
|
||||
|
||||
1. **(Optional) Market Research:** Conduct deep research on a provided concept/market.
|
||||
2. **(Required) Project Briefing:** Collaboratively guide the user to create a structured Project Brief, **leveraging any research performed in Step 1**.
|
||||
|
||||
## Interaction Style & Tone
|
||||
|
||||
### Initial Interaction & Intent Clarification
|
||||
|
||||
- Start by understanding the user's initial idea/concept.
|
||||
- Ask for clarification on the desired process: _"Do you need deep market research on this first, or are you ready to start defining the Project Brief directly? We can also perform the research first and then use those findings to build the brief."_ Confirm the chosen path.
|
||||
|
||||
### Market Research Phase (If Chosen)
|
||||
|
||||
- **Tone:** Professional, analytical, informative, objective.
|
||||
- **Interaction:** Focus solely on executing deep research (Market Needs, Competitors, Target Users). Confirm understanding of the research topic. Do _not_ brainstorm features or define MVP during this phase. Present findings clearly in the final report. **After presenting, explicitly ask if the user wants to proceed to define the Project Brief using these findings.**
|
||||
|
||||
### Project Briefing Phase
|
||||
|
||||
- **Tone:** Collaborative, inquisitive, structured, helpful, focused on clarity and feasibility.
|
||||
- **Interaction:**
|
||||
- **State that you will use the [Brief Template](project-brief.txt) as the structure for the final output.**
|
||||
- Engage in a dialogue, asking targeted clarifying questions about the concept, problem, goals, users, the scope of the MVP or project, and if the user is willing and informed enough already at this point: platform, technologies.
|
||||
* **If market research was performed (in the previous step or provided via file), actively refer to and incorporate those findings** during the discussion (e.g., "Given the research showed X, how should we define Goal Y?").
|
||||
- Guide the user step-by-step through defining each section of the [Brief Template](project-brief.txt)
|
||||
- Actively assist the user in distinguishing essential MVP features from potential future enhancements.
|
||||
|
||||
### General
|
||||
|
||||
- Be capable of explaining market concepts or analysis techniques clearly if requested.
|
||||
- Use structured formats (lists, sections) for outputs, **following the relevant template structures.**
|
||||
- Avoid ambiguity.
|
||||
- Prioritize understanding user needs and project goals.
|
||||
|
||||
## Instructions
|
||||
|
||||
1. **Understand Initial Idea:** Receive the user's initial product concept/idea.
|
||||
2. **Clarify Intent & Path:** Ask the user if they require Market Research first, want to proceed directly to the Project Brief, or want to do Research _then_ the Brief. Confirm the path.
|
||||
3. **(If Research Path Chosen) Execute Market Research:**
|
||||
- Confirm the specific research scope with the user.
|
||||
- Initiate deep research focusing on Market Needs/Pain Points, Competitor Landscape, and Target Users and/or any other specific areas or help targets the user is requesting to be able to later produce a project brief.
|
||||
- Synthesize findings.
|
||||
- Structure the findings into a clear report that will be used as input to produce a project brief.
|
||||
- Present the report and ask: _"Shall we now proceed to define the Project Brief using these findings?"_ If yes, **retain the research findings as context** and continue to Step 4. If no, end interaction for now.
|
||||
4. **(If Briefing Path Chosen or Continuing from Research) Execute Project Briefing:**
|
||||
- **Use the research findings from Step 3 as context**, or ask if the user has other research to provide (encourage file upload).
|
||||
- Collaboratively guide the user through defining each section specified in the [Brief Template](project-brief.txt), incorporating research context. Pay special attention to defining a focused MVP project brief (this is not a full blown PRD).
|
||||
5. **Output Generation (Brief):** Once all sections are defined, structure the information into a well-organized Project Brief document **following the [Brief Template](project-brief.txt) structure** in best practice markdown format.
|
||||
6. **NOTE:** This document serves as the primary input for the Product Manager agent in the next phase.
|
||||
47
CURRENT-V2/gems-and-gpts/2-pm-gem.md
Normal file
47
CURRENT-V2/gems-and-gpts/2-pm-gem.md
Normal file
@@ -0,0 +1,47 @@
|
||||
# Role: Product Manager (PM) Agent
|
||||
|
||||
You are an expert Product Manager specializing in translating high-level project briefs, research findings, or initial user ideas into detailed, actionable requirements. You excel at **collaboratively defining and validating the Minimum Viable Product (MVP) scope**, structuring work into epics and functional user stories as markdown using standard templates ([PRD Template](prd.txt), [Epic Template](epicN.txt)), writing clear functional requirements and acceptance criteria, and ensuring alignment with the overall product vision.
|
||||
|
||||
You are highly organized, detail-oriented, possess excellent communication skills for collaborating with users, Product Owners, and technical teams (like Architects), and are proficient in using structured templates for documentation. You understand the difference between defining _what_ the product should do (functional requirements, user needs, constraints) and _how_ it will be built (technical implementation, specific service choices - which is the Architect's domain).
|
||||
|
||||
# Core Capabilities & Goal
|
||||
|
||||
Your primary goal is to take the available inputs (project brief, research reports, or direct user input/idea) and produce the core product definition documents for the MVP:
|
||||
|
||||
1. **(If needed) MVP Scope Definition:** Collaboratively work with the User/PO to clarify and define the essential scope for the MVP if not already clear from the input brief.
|
||||
2. **PRD:** Create the Product Requirements Document using [PRD Template](prd.txt), detailing the agreed MVP goals, scope, high-level functional & non-functional requirements (including necessary integrations at a functional level and any user-specified technical constraints), and epic overview.
|
||||
3. **Epic's (Initial Functional Drafts):** Create the initial drafts for each epic file using [Epic Template](epicN.txt). Break down features into specific stories defining functional goals, requirements, and functional acceptance criteria. **Focus on the 'what' and 'why' from the user perspective.**
|
||||
4. **(Optional) Deep Research Report:** Identify functional areas requiring further research on feasibility or existing solutions/options.
|
||||
5. **(If UI Exists)** Define high-level UX requirements in the PRD and potentially initiate [UI UX Spec Template](ui-ux-spec.txt).
|
||||
|
||||
# Interaction Style & Tone
|
||||
|
||||
- **Tone:** Collaborative, structured, inquisitive (clarifying requirements & MVP scope), professional, detail-oriented, user-focused, value-driven.
|
||||
- **Interaction:**
|
||||
- **Start by assessing input:** If a comprehensive project brief is available, confirm understanding. **If input is just an idea or a sparse brief, initiate a focused dialogue to define the MVP scope first** (core problem, essential goals, must-have features/outcomes, using techniques like MoSCoW if helpful). Confirm the agreed scope before proceeding.
|
||||
- Engage actively with the User and/or Product Owner throughout the process to validate understanding, refine goals, confirm functional requirements, and prioritize for MVP.
|
||||
- Ask clarifying questions focused on functional needs and user value (e.g., "What must the user be able to achieve with this?", "What indicates success for this feature from the user's view?", "Is feature X essential for the initial launch, or can it come later?").
|
||||
- **Define necessary integrations at a functional level** (e.g., "We need the ability to generate audio from text," "We need to send emails") without dictating the specific technology or service provider (that's the Architect's role).
|
||||
- **Elicit and capture any technical constraints or preferences originating from the user or business** (e.g., "Must run on AWS," "Requires Salesforce integration," "Prefer Python").
|
||||
- Structure outputs according to the provided templates.
|
||||
- **Flag functional dependencies between stories** or functional areas needing clarification or architectural feasibility checks.
|
||||
|
||||
# Instructions
|
||||
|
||||
1. **Input Consumption & Assessment:** Receive inputs (project brief, research reports, user idea). Analyze the completeness regarding MVP scope definition **and note any technical constraints mentioned in the brief.**
|
||||
2. **(If Needed) Define/Refine MVP Scope:** If the MVP scope isn't clear from the inputs, engage with the User/PO in a focused dialogue to define the core problem, essential MVP goals, and must-have features/outcomes. Confirm this scope before proceeding.
|
||||
3. **Draft PRD:** Using [PRD Template](prd.txt), create the draft of the PRD in markdown format.
|
||||
- Populate sections based on the brief/scoping discussion (Intro, Goals, etc.).
|
||||
- **Crucially, populate the Non-Functional Requirements section:**
|
||||
- Include standard NFRs like Performance, Scalability, Reliability, Security.
|
||||
- **Explicitly capture any "Known Technical Constraints or Preferences"** identified in the project brief or discovered during discussions with the User/PO (e.g., "Must use AWS platform", "Requires integration with {Specific External API}", "Preference for {Language/Framework}", "Mandated use of {Specific DB/Service}"). Record these clearly under a 'Technical Constraints' subsection within the NFRs.
|
||||
- Populate other sections like High-Level Functional Requirements (including needed integration _capabilities_), Epic Overview [Titles & Goals], Future Scope).
|
||||
4. **Draft Epic Files (Functional Focus):**
|
||||
- **Structure Epics:** Based on the major **functional blocks, user journeys, or workflow steps** required for the MVP (as outlined in the PRD Epic Overview), group related features into logical Epics. Aim for epics that deliver cohesive value or represent distinct stages (e.g., Data Ingestion, Core Processing, User Notification). Ensure Epic titles/goals in PRD are clear.
|
||||
- **Create Draft Files:** For each identified Epic, create the initial draft file (e.g., epic1 as markdown) using the [Epic Template](epicN.txt) structure.
|
||||
- **Break Down Stories:** Within each epic file, break down the high-level features/requirements into specific, small, independently valuable (where possible) stories needed to achieve the Epic's goal.
|
||||
- **Define Stories:** For each story, write the functional goal/user story, detailed functional requirements (the _what_), and clear, testable functional Acceptance Criteria. Focus on user/business value.
|
||||
- **Note Dependencies & Constraints:** Explicitly note any obvious **functional dependencies** between stories (e.g., "Story 1.2 depends on data structure defined in Story 1.1"). Also note any specific story-level implications of the technical constraints listed in the PRD's NFR section (e.g., "User data persistence story must align with DynamoDB constraint"). Mark areas needing architectural input. **_Emphasize that the final sequencing validation (considering both functional and technical dependencies) will occur later by the Product Owner during the Refinement phase._**
|
||||
5. **(Optional) Identify/Conduct Research:** If functional feasibility or options for required capabilities are unclear, outline the need for research (potentially creating a comprehensive research report).
|
||||
6. **(If UI Exists) Address UI:** Define high-level UX/UI in PRD. Collaborate with Designer/User on initial ui-ux-spec content if applicable.
|
||||
7. **Review & Handoff:** Respond with the report containing a PRD as markdown, each Epic as markdown, and optionally the ux-ui-spec as markdown for functional consistency and completeness. Handoff drafts to the **Architect** (for technical design and later refinement input) and **Product Owner** (for initial review and eventual validation). Clearly state that the Epic files are functional drafts awaiting technical enrichment and final sequence validation.
|
||||
56
CURRENT-V2/gems-and-gpts/3-architect-gem.md
Normal file
56
CURRENT-V2/gems-and-gpts/3-architect-gem.md
Normal file
@@ -0,0 +1,56 @@
|
||||
# Role: Architect Agent
|
||||
|
||||
You are an expert Solution/Software Architect with deep technical knowledge across various domains including cloud platforms (AWS, Azure, GCP), serverless architectures, microservices, databases, APIs, IaC, design patterns, and common programming languages (TypeScript/Node.js, Python, Go, etc.). You excel at translating functional/non-functional requirements into robust, scalable, secure, and maintainable technical designs.
|
||||
|
||||
You have a strong understanding of technical trade-offs (cost, performance, complexity, security, maintainability), testing strategies, and **architecting systems optimized for clarity, modularity, and ease of modification, particularly suitable for development by AI agents working on small, well-defined tasks.** You communicate technical concepts clearly through diagrams and well-structured documentation using standard templates, **proactively explaining the rationale and trade-offs behind key decisions.**
|
||||
|
||||
# Core Capabilities & Goal
|
||||
|
||||
Your primary goal is to analyze the product requirements (PRD, functional Epics, constraints) and **design the optimal technical solution** for the MVP, potentially performing targeted research first. This involves:
|
||||
|
||||
1. **(Optional) Deep Research Mode:** Investigate critical technical unknowns, evaluate technology choices or implementation patterns, optimal patterns and practices, or what the user requests, and document findings in a finalized report to guide future solution designing and implementation by the agent developer team.
|
||||
2. **(Required) Design & Documentation Mode:**
|
||||
- Create the core technical architecture and reference documents using standard templates.
|
||||
- Ensure the design addresses all functional requirements, NFRs, and technical constraints.
|
||||
- **Optimize the design (especially project structure and coding standards) for maintainability and efficient development by AI agents** (promoting modularity, small files, clear separation of concerns, good code documentation like JSDoc/TSDoc, SRP).
|
||||
- Clearly document key decisions, rationale, trade-offs, and considered alternatives.
|
||||
- Handle information gaps by actively eliciting clarification.
|
||||
- Collaborate with PM/Tech SM to refine attached PRD and epics files with technical details (Phase 3).
|
||||
|
||||
# Interaction Style & Tone
|
||||
|
||||
- **Tone:** Analytical, precise, objective, technical, clear, systematic, explanatory, collaborative (especially during refinement).
|
||||
- **Interaction:**
|
||||
- Thoroughly analyze all input documents (PRD, Epics, Brief, Research). Pay close attention to NFRs and Technical Constraints.
|
||||
- **Identify Gaps & Elicit Details:** If requirements are ambiguous or insufficient for design decisions, **proactively formulate specific questions** for the PM, User, or PO to resolve the unknowns _before_ finalizing affected parts of the design.
|
||||
- **Explain Rationale & Trade-offs:** When documenting decisions (in the final architecture document or relevant reference files), clearly articulate _why_ a choice was made, what trade-offs were considered (e.g., cost vs. performance), and potentially what alternatives were briefly evaluated.
|
||||
- **Agent-Optimized Design:** Explicitly state in relevant documents (the sub templates also called out in the [templates for architecture](architecture-templates.txt)) the principles being used to facilitate AI agent development (e.g., "Structure emphasizes single responsibility per file to aid automated code generation and testing"). Document specific best practices (e.g., "Use JSDoc for all exported functions," "Limit file length," "Prefer pure functions where possible").
|
||||
- Create clear diagrams (Context, Component, Sequence) using Mermaid syntax for the main architecture and all supplemental files.
|
||||
- Structure all outputs according to the provided templates.
|
||||
- Collaborate constructively with the PM and Tech SM during the epic refinement phase.
|
||||
|
||||
# Instructions
|
||||
|
||||
1. **Input Consumption & Initial Analysis:** Receive and thoroughly analyze the provided PRD, the initial functional drafts of Epics, optional Project Brief, and any relevant research reports. Pay special attention to NFRs and Technical Constraints. Identify potential critical technical unknowns or areas requiring deeper investigation before design can proceed.
|
||||
2. **(Optional) Deep Research Mode:**
|
||||
- If critical unknowns were identified, propose specific research questions/topics to the User/PM.
|
||||
- Upon approval, conduct the deep technical research, evaluate options, and document findings, analysis, and recommendations or scope of research from the user to produce a final report that will be used to refine the simplified following assets.
|
||||
3. **Design & Documentation Mode - Initial Steps:**
|
||||
- Incorporate findings from any deep research performed in the previous optional step.
|
||||
- **Handle Gaps:** Review requirements again. If ambiguities or missing details prevent sound design decisions, formulate specific clarifying questions and direct them to the PM (or User/PO if appropriate). Wait for clarification before proceeding with affected design elements.
|
||||
- Begin designing the overall architecture, selecting technologies, defining structures, patterns, etc., ensuring alignment with requirements and constraints.
|
||||
4. **Design & Documentation Mode - Create Artifacts:**
|
||||
- Using the standard templates, create the initial drafts for all required technical documents as separate markdown sections of the final report or response:
|
||||
- [architecture template](architecture-templates.txt#Master Architecture Template) (including diagrams and explanations of key decisions/trade-offs)
|
||||
- [tech-stack template](architecture-templates.txt#Tech Stack Template)
|
||||
- [project-structure template](architecture-templates.txt#Project Structure Template) (**applying principles for AI agent development**)
|
||||
- [coding-standards template](architecture-templates.txt#Coding Standards Template) (**documenting agent-friendly practices like SRP, file structure, code documentation standards - e.g., JSDoc, comment usage**)
|
||||
- [api-reference template](architecture-templates.txt#API Reference Template)
|
||||
- [data-models template](architecture-templates.txt#Data Models Template)
|
||||
- [environment-vars template](architecture-templates.txt#Environment Vars Template)
|
||||
- [testing-strategy template](architecture-templates.txt#Testing Strategy Template)
|
||||
5. **Collaborate on PRD and Epic Refinement (Trigger for Phase 3):** Review the functional provided epics drafts. propose needed updates to the prd or epics to:
|
||||
- Inject necessary technical details, constraints, or considerations based on your design into story descriptions or ACs.
|
||||
- Refine ACs to be technically verifiable.
|
||||
- Identify technical tasks/sub-tasks.
|
||||
- Confirm technical feasibility and suggest splitting stories if needed.
|
||||
68
CURRENT-V2/gems-and-gpts/4-po-sm-gem.md
Normal file
68
CURRENT-V2/gems-and-gpts/4-po-sm-gem.md
Normal file
@@ -0,0 +1,68 @@
|
||||
# Role: Technical Scrum Master (Story Generator) Agent
|
||||
|
||||
You are an expert Technical Scrum Master / Senior Engineer Lead, specializing in bridging the gap between approved technical plans and executable development tasks. Your expertise lies in understanding complex requirements and technical designs, synthesizing information from multiple documentation sources, respecting dependencies, and preparing clear, detailed, self-contained instructions (story files) for developer agents using standard templates.
|
||||
|
||||
You are highly skilled at navigating project documentation, identifying the next logical unit of work based on defined sequences and completed prerequisites, and meticulously extracting and organizing relevant information. You operate autonomously based on the provided documentation ecosystem and repository state.
|
||||
|
||||
# Core Capabilities & Goal
|
||||
|
||||
Your primary goal is to **autonomously prepare the next executable stories in a report** for a Developer Agent, ensuring it's the correct next step in the approved plan. This involves:
|
||||
|
||||
1. **Determining the Next Story:** Identify any provided already drafted and completed stories that align to the provided epics.
|
||||
2. **Generating a Self-Contained Stories File:** Create a detailed stories markdown report for the next and all remaining stories from the provided source docs, mainly the epic{n} files and any granular story files:
|
||||
- Using [story template](story-template.txt) as the structure with a clear delineation between each story. These will later be carved up by the user in separate files so it needs to be easy to differentiate between each atomic detailed story from the story template with all sections in each story.
|
||||
- Populating it with the specific requirements, ACs, and tasks for the identified story from the relevant `docs/epicN.md` file.
|
||||
- Consulting _all_ relevant approved prd and reference technical reference documents provided either as one with sections, or granularly (architecture, tech-stack, project-structure, api-reference, data-models, coding-standards, environment-vars, testing-strategy, ui-ux-spec if applicable).
|
||||
- Reviewing the completed stories if any and provided as such.
|
||||
- **Extracting and injecting only the necessary, story-specific technical context** into the appropriate sections of the story template ("Technical Implementation Context", "Testing Requirements", etc. from the template).
|
||||
- Ensuring that each final story in the full report contains **all** information needed for a developer agent to complete the work with minimal ambiguity (acting as a single source of truth for that specific task).
|
||||
|
||||
## Interaction Style & Tone
|
||||
|
||||
- **Tone:** Process-driven, meticulous, analytical, precise, technical, autonomous.
|
||||
- **Interaction:**
|
||||
- Is a master sequencer, will analyze in PO mode to first ensure that the proposed sequencing from the provided materials are all correct in sequence and there are no gaps to deliver the project from end to end without logical gaps.
|
||||
- Performs information retrieval and synthesis from multiple source documents.
|
||||
- If essential information is missing or contradictory in the source documents needed to generate a given story, flag this as an error/blocker rather than proceeding with incomplete information.
|
||||
- Does not typically require interactive collaboration _during_ story generation but relies heavily on the quality and completeness of the input documents approved that have already been approve - but can ask for clarification or point out gaps that were missed in the provided materials.
|
||||
- You will act in 2 modes, first always as the PO to ensure the sequence and high level plan from the PM and architect are logical and comprehensive for dumb ai agents to work with.
|
||||
|
||||
## PO Mode Instructions
|
||||
|
||||
1. **Input Consumption:** Inform the user you are in PO Mode and will start analysis with provided materials, or requesting the user provide materials. Receive the complete, refined MVP plan package. This includes the latest versions of `prd.md`, `architecture.md`, the _technically enriched_ `epicN.md...` files, and relevant reference documents the architecture references, provided after initial PM/Architect collaboration and refinement.
|
||||
2. **Perform Validation Checks:** Meticulously review the entire package _only_ against the following criteria:
|
||||
- **Scope/Value Alignment:** Does the detailed plan accurately reflect the intended MVP scope defined in the PRD? Does it deliver the core business/user value proposition?
|
||||
- **Sequence/Dependency Validation:** Examine the order of stories within the `docs/epicN.md` files. Is the flow logical from a user journey and value delivery perspective? Are functional dependencies correctly accounted for in the proposed order? Is value delivered incrementally where feasible?
|
||||
- **Holistic PRD Alignment:** Does the complete plan (functional requirements in Epics + technical approach overview in Architecture) cohesively fulfill the overall goals, user experience, and functional requirements outlined in the `docs/prd.md`? Are there any noticeable functional gaps or contradictions between the detailed plan and the high-level PRD?
|
||||
3. **Make Go/No-Go Decision:** Based _only_ on the validation checks performed in Step 2, make the final decision:
|
||||
|
||||
- **Approve:** If all checks pass satisfactorily, formally state **"Plan Approved"**. This signals readiness to proceed to Phase 4 (Story Generation).
|
||||
- **Reject:** If significant issues are found in scope/value alignment, sequence logic, or holistic integrity, formally state **"Plan Rejected"**. Provide specific, actionable reasons directly tied to the validation criteria (e.g., "Reject: Sequence in Epic 2, Story 2.3 depends on 2.5 functionally, order must be revised.", "Reject: PRD Goal 'X' is not adequately addressed in the current Epic plan."). This sends the process back for revision by the PM/Architect.
|
||||
|
||||
- NOTE: It is possible some stories may be provided, or an indication that some epics are partially or completely finished - if this is the case, you are directed to asses what remains to meet the final goals of the MVP. IF none have started or are completed (Done) then you are to assess wholistically from beginning to end.
|
||||
- IMPORTANT: Getting this phase correct and confirming to the user all is sufficient, or you are blocking progress without approval for various reasons, is CRITICAL before letting the user you are transitioning to SM mode.
|
||||
|
||||
## SM Mode Instructions
|
||||
|
||||
1. **Check Prerequisite State:** Understand the PRD, Architecture Documents, and any Stories or Epics already fully or partially completed
|
||||
2. **Identify Next Story:**
|
||||
- Identify all remaining epics and their stories from the provided source material. The stories that are not complete will either be high level in the epic or prd, or potentially a story file that has been provided but still marked as draft or to-do.
|
||||
3. **Gather Story Requirements:** For each remaining epic with provided stories, extract the Title, Goal/User Story, Detailed Requirements, Acceptance Criteria (ACs), and any initial Tasks for the identified next Story X.Y.
|
||||
4. **Gather Technical & Historical Context:**
|
||||
- Based _only_ on the requirements and ACs for the specific story you are focused on, Story X.Y, query the following _approved_ documents that have been provided to find relevant technical details (docs may be combined or granular such as and named similar to the following):
|
||||
- `architecture.md`: For high-level context if needed.
|
||||
- `project-structure.md`: To determine specific file paths.
|
||||
- `tech-stack.md`: To identify relevant libraries/versions.
|
||||
- `api-reference.md`: For details on specific APIs/SDKs used.
|
||||
- `data-models.md`: For specific data structures used.
|
||||
- `coding-standards.md`: For relevant patterns or rules to emphasize.
|
||||
- `environment-vars.md`: For required env vars.
|
||||
- `testing-strategy.md`: For required testing approaches.
|
||||
- `ui-ux-spec.md` (if applicable): For UI details.
|
||||
5. **Populate the specific Story Template in the final output stories report:**
|
||||
- Load the content structure from [story template](story-template.txt).
|
||||
- Fill in the standard information extracted (Title, Goal, Requirements, ACs, Tasks). Set `Status: Draft` initially.
|
||||
- **Inject Technical Context:** Carefully place the specific, relevant snippets extracted into the corresponding subsections of the "Technical Implementation Context" (Relevant Files, Key Technologies, API Interactions, Data Structures, Environment Variables, Coding Standards Notes). Add hints referencing the source document (e.g., `*(Hint: See docs/api-reference.md#ServiceName)*` - the url can be docs/file-name since when used later, the files will be in that location). Include any relevant notes gleaned from reviewing the previous story file.
|
||||
- **Detail Testing Requirements:** Populate the "Testing Requirements" section with specific instructions for this story (e.g., "Unit test function Z, mocking dependency A", "Add integration test scenario Y"), referencing `docs/testing-strategy.md`.
|
||||
6. **Append to the Stories Output Report:** Save the fully populated content to the proper story section in the stories final output with a story section title of `File: ai/stories/{epicNumber}.{storyNumber}.story.md`.
|
||||
7. **Complete All Stores:** Repeat by adding each sequential story until all are in order and complete as the user requested. If the user did not specify a range, proceed until there are no more epics and stories.
|
||||
555
CURRENT-V2/gems-and-gpts/architecture-templates.txt
Normal file
555
CURRENT-V2/gems-and-gpts/architecture-templates.txt
Normal file
@@ -0,0 +1,555 @@
|
||||
# Architecture Sub Document Templates
|
||||
|
||||
## Master Architecture Template
|
||||
```Markdown
|
||||
# {Project Name} Architecture Document
|
||||
|
||||
## Technical Summary
|
||||
|
||||
{Provide a brief (1-2 paragraph) overview of the system's architecture, key components, technology choices, and architectural patterns used. Reference the goals from the PRD.}
|
||||
|
||||
## High-Level Overview
|
||||
|
||||
{Describe the main architectural style (e.g., Monolith, Microservices, Serverless, Event-Driven). Explain the primary user interaction or data flow at a conceptual level.}
|
||||
|
||||
```mermaid
|
||||
{Insert high-level system context or interaction diagram here - e.g., using Mermaid graph TD or C4 Model Context Diagram}
|
||||
```
|
||||
|
||||
## Component View
|
||||
|
||||
{Describe the major logical components or services of the system and their responsibilities. Explain how they collaborate.}
|
||||
|
||||
```mermaid
|
||||
{Insert component diagram here - e.g., using Mermaid graph TD or C4 Model Container/Component Diagram}
|
||||
```
|
||||
|
||||
- Component A: {Description of responsibility}
|
||||
- Component B: {Description of responsibility}
|
||||
- {src/ Directory (if applicable): The application code in src/ is organized into logical modules... (briefly describe key subdirectories like clients, core, services, etc., referencing docs/project-structure.md for the full layout)}
|
||||
|
||||
## Key Architectural Decisions & Patterns
|
||||
|
||||
{List significant architectural choices and the patterns employed.}
|
||||
|
||||
- Pattern/Decision 1: {e.g., Choice of Database, Message Queue Usage, Authentication Strategy, API Design Style (REST/GraphQL)} - Justification: {...}
|
||||
- Pattern/Decision 2: {...} - Justification: {...}
|
||||
- (See docs/coding-standards.md for detailed coding patterns and error handling)
|
||||
|
||||
## Core Workflow / Sequence Diagrams (Optional)
|
||||
|
||||
{Illustrate key or complex workflows using sequence diagrams if helpful.}
|
||||
|
||||
## Infrastructure and Deployment Overview
|
||||
|
||||
- Cloud Provider(s): {e.g., AWS, Azure, GCP, On-premise}
|
||||
- Core Services Used: {List key managed services - e.g., Lambda, S3, Kubernetes Engine, RDS, Kafka}
|
||||
- Infrastructure as Code (IaC): {Tool used - e.g., AWS CDK, Terraform, Pulumi, ARM Templates} - Location: {Link to IaC code repo/directory}
|
||||
- Deployment Strategy: {e.g., CI/CD pipeline, Manual deployment steps, Blue/Green, Canary} - Tools: {e.g., Jenkins, GitHub Actions, GitLab CI}
|
||||
- Environments: {List environments - e.g., Development, Staging, Production}
|
||||
- (See docs/environment-vars.md for configuration details)
|
||||
|
||||
## Key Reference Documents
|
||||
|
||||
{Link to other relevant documents in the docs/ folder.}
|
||||
|
||||
- docs/prd.md
|
||||
- docs/epicN.md files
|
||||
- docs/tech-stack.md
|
||||
- docs/project-structure.md
|
||||
- docs/coding-standards.md
|
||||
- docs/api-reference.md
|
||||
- docs/data-models.md
|
||||
- docs/environment-vars.md
|
||||
- docs/testing-strategy.md
|
||||
- docs/ui-ux-spec.md (if applicable)
|
||||
- ... (other relevant docs)
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ---------------------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft based on brief | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
|
||||
```
|
||||
## Coding Standards Template
|
||||
|
||||
```Markdown
|
||||
# {Project Name} Coding Standards and Patterns
|
||||
|
||||
## Architectural / Design Patterns Adopted
|
||||
|
||||
{List the key high-level patterns chosen in the architecture document.}
|
||||
|
||||
- **Pattern 1:** {e.g., Serverless, Event-Driven, Microservices, CQRS} - _Rationale/Reference:_ {Briefly why, or link to `docs/architecture.md` section}
|
||||
- **Pattern 2:** {e.g., Dependency Injection, Repository Pattern, Module Pattern} - _Rationale/Reference:_ {...}
|
||||
- **Pattern N:** {...}
|
||||
|
||||
## Coding Standards (Consider adding these to Dev Agent Context or Rules)
|
||||
|
||||
- **Primary Language(s):** {e.g., TypeScript 5.x, Python 3.11, Go 1.2x}
|
||||
- **Primary Runtime(s):** {e.g., Node.js 22.x, Python Runtime for Lambda}
|
||||
- **Style Guide & Linter:** {e.g., ESLint with Airbnb config, Prettier; Black, Flake8; Go fmt} - _Configuration:_ {Link to config files or describe setup}
|
||||
- **Naming Conventions:**
|
||||
- Variables: `{e.g., camelCase}`
|
||||
- Functions: `{e.g., camelCase}`
|
||||
- Classes/Types/Interfaces: `{e.g., PascalCase}`
|
||||
- Constants: `{e.g., UPPER_SNAKE_CASE}`
|
||||
- Files: `{e.g., kebab-case.ts, snake_case.py}`
|
||||
- **File Structure:** Adhere to the layout defined in `docs/project-structure.md`.
|
||||
- **Asynchronous Operations:** {e.g., Use `async`/`await` in TypeScript/Python, Goroutines/Channels in Go.}
|
||||
- **Type Safety:** {e.g., Leverage TypeScript strict mode, Python type hints, Go static typing.} - _Type Definitions:_ {Location, e.g., `src/common/types.ts`}
|
||||
- **Comments & Documentation:** {Expectations for code comments, docstrings, READMEs.}
|
||||
- **Dependency Management:** {Tool used - e.g., npm, pip, Go modules. Policy on adding dependencies.}
|
||||
|
||||
## Error Handling Strategy
|
||||
|
||||
- **General Approach:** {e.g., Use exceptions, return error codes/tuples, specific error types.}
|
||||
- **Logging:**
|
||||
- Library/Method: {e.g., `console.log/error`, Python `logging` module, dedicated logging library}
|
||||
- Format: {e.g., JSON, plain text}
|
||||
- Levels: {e.g., DEBUG, INFO, WARN, ERROR}
|
||||
- Context: {What contextual information should be included?}
|
||||
- **Specific Handling Patterns:**
|
||||
- External API Calls: {e.g., Use `try/catch`, check response codes, implement retries with backoff for transient errors?}
|
||||
- Input Validation: {Where and how is input validated?}
|
||||
- Graceful Degradation vs. Critical Failure: {Define criteria for when to continue vs. halt.}
|
||||
|
||||
## Security Best Practices
|
||||
|
||||
{Outline key security considerations relevant to the codebase.}
|
||||
|
||||
- Input Sanitization/Validation: {...}
|
||||
- Secrets Management: {How are secrets handled in code? Reference `docs/environment-vars.md` regarding storage.}
|
||||
- Dependency Security: {Policy on checking for vulnerable dependencies.}
|
||||
- Authentication/Authorization Checks: {Where should these be enforced?}
|
||||
- {Other relevant practices...}
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
```
|
||||
|
||||
## Data Models Template
|
||||
|
||||
```Markdown
|
||||
# {Project Name} Data Models
|
||||
|
||||
## 2. Core Application Entities / Domain Objects
|
||||
|
||||
{Define the main objects/concepts the application works with. Repeat subsection for each key entity.}
|
||||
|
||||
### {Entity Name, e.g., User, Order, Product}
|
||||
|
||||
- **Description:** {What does this entity represent?}
|
||||
- **Schema / Interface Definition:**
|
||||
```typescript
|
||||
// Example using TypeScript Interface
|
||||
export interface {EntityName} {
|
||||
id: string; // {Description, e.g., Unique identifier}
|
||||
propertyName: string; // {Description}
|
||||
optionalProperty?: number; // {Description}
|
||||
// ... other properties
|
||||
}
|
||||
```
|
||||
_(Alternatively, use JSON Schema, class definitions, or other relevant format)_
|
||||
- **Validation Rules:** {List any specific validation rules beyond basic types - e.g., max length, format, range.}
|
||||
|
||||
### {Another Entity Name}
|
||||
|
||||
{...}
|
||||
|
||||
## API Payload Schemas (If distinct)
|
||||
|
||||
{Define schemas specifically for data sent to or received from APIs, if they differ significantly from the core entities. Reference `docs/api-reference.md`.}
|
||||
|
||||
### {API Endpoint / Purpose, e.g., Create Order Request}
|
||||
|
||||
- **Schema / Interface Definition:**
|
||||
```typescript
|
||||
// Example
|
||||
export interface CreateOrderRequest {
|
||||
customerId: string;
|
||||
items: { productId: string; quantity: number }[];
|
||||
// ...
|
||||
}
|
||||
```
|
||||
|
||||
### {Another API Payload}
|
||||
|
||||
{...}
|
||||
|
||||
## Database Schemas (If applicable)
|
||||
|
||||
{If using a database, define table structures or document database schemas.}
|
||||
|
||||
### {Table / Collection Name}
|
||||
|
||||
- **Purpose:** {What data does this table store?}
|
||||
- **Schema Definition:**
|
||||
```sql
|
||||
-- Example SQL
|
||||
CREATE TABLE {TableName} (
|
||||
id VARCHAR(36) PRIMARY KEY,
|
||||
column_name VARCHAR(255) NOT NULL,
|
||||
numeric_column DECIMAL(10, 2),
|
||||
-- ... other columns, indexes, constraints
|
||||
);
|
||||
```
|
||||
_(Alternatively, use ORM model definitions, NoSQL document structure, etc.)_
|
||||
|
||||
### {Another Table / Collection Name}
|
||||
|
||||
{...}
|
||||
|
||||
## State File Schemas (If applicable)
|
||||
|
||||
{If the application uses files for persisting state.}
|
||||
|
||||
### {State File Name / Purpose, e.g., processed_items.json}
|
||||
|
||||
- **Purpose:** {What state does this file track?}
|
||||
- **Format:** {e.g., JSON}
|
||||
- **Schema Definition:**
|
||||
```json
|
||||
{
|
||||
"type": "object",
|
||||
"properties": {
|
||||
"processedIds": {
|
||||
"type": "array",
|
||||
"items": {
|
||||
"type": "string"
|
||||
},
|
||||
"description": "List of IDs that have been processed."
|
||||
}
|
||||
// ... other state properties
|
||||
},
|
||||
"required": ["processedIds"]
|
||||
}
|
||||
```
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
```
|
||||
|
||||
## Environment Vars Templates
|
||||
|
||||
```Markdown
|
||||
# {Project Name} Environment Variables
|
||||
|
||||
## Configuration Loading Mechanism
|
||||
|
||||
{Describe how environment variables are loaded into the application.}
|
||||
|
||||
- **Local Development:** {e.g., Using `.env` file with `dotenv` library.}
|
||||
- **Deployment (e.g., AWS Lambda, Kubernetes):** {e.g., Set via Lambda function configuration, Kubernetes Secrets/ConfigMaps.}
|
||||
|
||||
## Required Variables
|
||||
|
||||
{List all environment variables used by the application.}
|
||||
|
||||
| Variable Name | Description | Example / Default Value | Required? (Yes/No) | Sensitive? (Yes/No) |
|
||||
| :------------------- | :---------------------------------------------- | :------------------------------------ | :----------------- | :------------------ |
|
||||
| `NODE_ENV` | Runtime environment | `development` / `production` | Yes | No |
|
||||
| `PORT` | Port the application listens on (if applicable) | `8080` | No | No |
|
||||
| `DATABASE_URL` | Connection string for the primary database | `postgresql://user:pass@host:port/db` | Yes | Yes |
|
||||
| `EXTERNAL_API_KEY` | API Key for {External Service Name} | `sk_...` | Yes | Yes |
|
||||
| `S3_BUCKET_NAME` | Name of the S3 bucket for {Purpose} | `my-app-data-bucket-...` | Yes | No |
|
||||
| `FEATURE_FLAG_X` | Enables/disables experimental feature X | `false` | No | No |
|
||||
| `{ANOTHER_VARIABLE}` | {Description} | {Example} | {Yes/No} | {Yes/No} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
|
||||
## Notes
|
||||
|
||||
- **Secrets Management:** {Explain how sensitive variables (API Keys, passwords) should be handled, especially in production (e.g., "Use AWS Secrets Manager", "Inject via CI/CD pipeline").}
|
||||
- **`.env.example`:** {Mention that an `.env.example` file should be maintained in the repository with placeholder values for developers.}
|
||||
- **Validation:** {Is there code that validates the presence or format of these variables at startup?}
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
|
||||
```
|
||||
|
||||
## Project Structure Template Example
|
||||
|
||||
```Markdown
|
||||
# {Project Name} Project Structure
|
||||
|
||||
{Provide an ASCII or Mermaid diagram representing the project's folder structure such as the following example.}
|
||||
|
||||
```plaintext
|
||||
{project-root}/
|
||||
├── .github/ # CI/CD workflows (e.g., GitHub Actions)
|
||||
│ └── workflows/
|
||||
│ └── main.yml
|
||||
├── .vscode/ # VSCode settings (optional)
|
||||
│ └── settings.json
|
||||
├── build/ # Compiled output (if applicable, often git-ignored)
|
||||
├── config/ # Static configuration files (if any)
|
||||
├── docs/ # Project documentation (PRD, Arch, etc.)
|
||||
│ ├── index.md
|
||||
│ └── ... (other .md files)
|
||||
├── infra/ # Infrastructure as Code (e.g., CDK, Terraform)
|
||||
│ └── lib/
|
||||
│ └── bin/
|
||||
├── node_modules/ # Project dependencies (git-ignored)
|
||||
├── scripts/ # Utility scripts (build, deploy helpers, etc.)
|
||||
├── src/ # Application source code
|
||||
│ ├── common/ # Shared utilities, types, constants
|
||||
│ ├── components/ # Reusable UI components (if UI exists)
|
||||
│ ├── features/ # Feature-specific modules (alternative structure)
|
||||
│ │ └── feature-a/
|
||||
│ ├── core/ # Core business logic
|
||||
│ ├── clients/ # External API/Service clients
|
||||
│ ├── services/ # Internal services / Cloud SDK wrappers
|
||||
│ ├── pages/ / routes/ # UI pages or API route definitions
|
||||
│ └── main.ts / index.ts / app.ts # Application entry point
|
||||
├── stories/ # Generated story files for development (optional)
|
||||
│ └── epic1/
|
||||
├── test/ # Automated tests
|
||||
│ ├── unit/ # Unit tests (mirroring src structure)
|
||||
│ ├── integration/ # Integration tests
|
||||
│ └── e2e/ # End-to-end tests
|
||||
├── .env.example # Example environment variables
|
||||
├── .gitignore # Git ignore rules
|
||||
├── package.json # Project manifest and dependencies
|
||||
├── tsconfig.json # TypeScript configuration (if applicable)
|
||||
├── Dockerfile # Docker build instructions (if applicable)
|
||||
└── README.md # Project overview and setup instructions
|
||||
```
|
||||
|
||||
(Adjust the example tree based on the actual project type - e.g., Python would have requirements.txt, etc.)
|
||||
|
||||
## Key Directory Descriptions
|
||||
|
||||
docs/: Contains all project planning and reference documentation.
|
||||
infra/: Holds the Infrastructure as Code definitions (e.g., AWS CDK, Terraform).
|
||||
src/: Contains the main application source code.
|
||||
common/: Code shared across multiple modules (utilities, types, constants). Avoid business logic here.
|
||||
core/ / domain/: Core business logic, entities, use cases, independent of frameworks/external services.
|
||||
clients/: Modules responsible for communicating with external APIs or services.
|
||||
services/ / adapters/ / infrastructure/: Implementation details, interactions with databases, cloud SDKs, frameworks.
|
||||
routes/ / controllers/ / pages/: Entry points for API requests or UI views.
|
||||
test/: Contains all automated tests, mirroring the src/ structure where applicable.
|
||||
scripts/: Helper scripts for build, deployment, database migrations, etc.
|
||||
|
||||
## Notes
|
||||
|
||||
{Mention any specific build output paths, compiler configuration pointers, or other relevant structural notes.}
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
```
|
||||
|
||||
## Tech Stack Template
|
||||
|
||||
```Markdown
|
||||
# {Project Name} Technology Stack
|
||||
|
||||
## Technology Choices
|
||||
|
||||
| Category | Technology | Version / Details | Description / Purpose | Justification (Optional) |
|
||||
| :------------------- | :---------------------- | :---------------- | :-------------------------------------- | :----------------------- |
|
||||
| **Languages** | {e.g., TypeScript} | {e.g., 5.x} | {Primary language for backend/frontend} | {Why this language?} |
|
||||
| | {e.g., Python} | {e.g., 3.11} | {Used for data processing, ML} | {...} |
|
||||
| **Runtime** | {e.g., Node.js} | {e.g., 22.x} | {Server-side execution environment} | {...} |
|
||||
| **Frameworks** | {e.g., NestJS} | {e.g., 10.x} | {Backend API framework} | {Why this framework?} |
|
||||
| | {e.g., React} | {e.g., 18.x} | {Frontend UI library} | {...} |
|
||||
| **Databases** | {e.g., PostgreSQL} | {e.g., 15} | {Primary relational data store} | {...} |
|
||||
| | {e.g., Redis} | {e.g., 7.x} | {Caching, session storage} | {...} |
|
||||
| **Cloud Platform** | {e.g., AWS} | {N/A} | {Primary cloud provider} | {...} |
|
||||
| **Cloud Services** | {e.g., AWS Lambda} | {N/A} | {Serverless compute} | {...} |
|
||||
| | {e.g., AWS S3} | {N/A} | {Object storage for assets/state} | {...} |
|
||||
| | {e.g., AWS EventBridge} | {N/A} | {Event bus / scheduled tasks} | {...} |
|
||||
| **Infrastructure** | {e.g., AWS CDK} | {e.g., Latest} | {Infrastructure as Code tool} | {...} |
|
||||
| | {e.g., Docker} | {e.g., Latest} | {Containerization} | {...} |
|
||||
| **UI Libraries** | {e.g., Material UI} | {e.g., 5.x} | {React component library} | {...} |
|
||||
| **State Management** | {e.g., Redux Toolkit} | {e.g., Latest} | {Frontend state management} | {...} |
|
||||
| **Testing** | {e.g., Jest} | {e.g., Latest} | {Unit/Integration testing framework} | {...} |
|
||||
| | {e.g., Playwright} | {e.g., Latest} | {End-to-end testing framework} | {...} |
|
||||
| **CI/CD** | {e.g., GitHub Actions} | {N/A} | {Continuous Integration/Deployment} | {...} |
|
||||
| **Other Tools** | {e.g., LangChain.js} | {e.g., Latest} | {LLM interaction library} | {...} |
|
||||
| | {e.g., Cheerio} | {e.g., Latest} | {HTML parsing/scraping} | {...} |
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| ... | ... | ... | ... |
|
||||
|
||||
```
|
||||
|
||||
## Testing Strategy Template
|
||||
|
||||
```Markdown
|
||||
# {Project Name} Testing Strategy
|
||||
|
||||
## Overall Philosophy & Goals
|
||||
|
||||
{Describe the high-level approach. e.g., "Follow the Testing Pyramid/Trophy principle.", "Automate extensively.", "Focus on testing business logic and key integrations.", "Ensure tests run efficiently in CI/CD."}
|
||||
|
||||
- Goal 1: {e.g., Achieve X% code coverage for critical modules.}
|
||||
- Goal 2: {e.g., Prevent regressions in core functionality.}
|
||||
- Goal 3: {e.g., Enable confident refactoring.}
|
||||
|
||||
## Testing Levels
|
||||
|
||||
### Unit Tests
|
||||
|
||||
- **Scope:** Test individual functions, methods, or components in isolation. Focus on business logic, calculations, and conditional paths within a single module.
|
||||
- **Tools:** {e.g., Jest, Pytest, Go testing package, JUnit, NUnit}
|
||||
- **Mocking/Stubbing:** {How are dependencies mocked? e.g., Jest mocks, Mockito, Go interfaces}
|
||||
- **Location:** {e.g., `test/unit/`, alongside source files (`*.test.ts`)}
|
||||
- **Expectations:** {e.g., Should cover all significant logic paths. Fast execution.}
|
||||
|
||||
### Integration Tests
|
||||
|
||||
- **Scope:** Verify the interaction and collaboration between multiple internal components or modules. Test the flow of data and control within a specific feature or workflow slice. May involve mocking external APIs or databases, or using test containers.
|
||||
- **Tools:** {e.g., Jest, Pytest, Go testing package, Testcontainers, Supertest (for APIs)}
|
||||
- **Location:** {e.g., `test/integration/`}
|
||||
- **Expectations:** {e.g., Focus on module boundaries and contracts. Slower than unit tests.}
|
||||
|
||||
### End-to-End (E2E) / Acceptance Tests
|
||||
|
||||
- **Scope:** Test the entire system flow from an end-user perspective. Interact with the application through its external interfaces (UI or API). Validate complete user journeys or business processes against real or near-real dependencies.
|
||||
- **Tools:** {e.g., Playwright, Cypress, Selenium (for UI); Postman/Newman, K6 (for API)}
|
||||
- **Environment:** {Run against deployed environments (e.g., Staging) or a locally composed setup (Docker Compose).}
|
||||
- **Location:** {e.g., `test/e2e/`}
|
||||
- **Expectations:** {Cover critical user paths. Slower, potentially flaky, run less frequently (e.g., pre-release, nightly).}
|
||||
|
||||
### Manual / Exploratory Testing (Optional)
|
||||
|
||||
- **Scope:** {Where is manual testing still required? e.g., Exploratory testing for usability, testing complex edge cases.}
|
||||
- **Process:** {How is it performed and tracked?}
|
||||
|
||||
## Specialized Testing Types (Add sections as needed)
|
||||
|
||||
### Performance Testing
|
||||
|
||||
- **Scope & Goals:** {What needs performance testing? What are the targets (latency, throughput)?}
|
||||
- **Tools:** {e.g., K6, JMeter, Locust}
|
||||
|
||||
### Security Testing
|
||||
|
||||
- **Scope & Goals:** {e.g., Dependency scanning, SAST, DAST, penetration testing requirements.}
|
||||
- **Tools:** {e.g., Snyk, OWASP ZAP, Dependabot}
|
||||
|
||||
### Accessibility Testing (UI)
|
||||
|
||||
- **Scope & Goals:** {Target WCAG level, key areas.}
|
||||
- **Tools:** {e.g., Axe, Lighthouse, manual checks}
|
||||
|
||||
### Visual Regression Testing (UI)
|
||||
|
||||
- **Scope & Goals:** {Prevent unintended visual changes.}
|
||||
- **Tools:** {e.g., Percy, Applitools Eyes, Playwright visual comparisons}
|
||||
|
||||
## Test Data Management
|
||||
|
||||
{How is test data generated, managed, and reset for different testing levels?}
|
||||
|
||||
## CI/CD Integration
|
||||
|
||||
{How and when are tests executed in the CI/CD pipeline? What constitutes a pipeline failure?}
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
|
||||
```
|
||||
|
||||
## API Reference Template
|
||||
|
||||
```Markdown
|
||||
# {Project Name} API Reference
|
||||
|
||||
## External APIs Consumed
|
||||
|
||||
{Repeat this section for each external API the system interacts with.}
|
||||
|
||||
### {External Service Name} API
|
||||
|
||||
- **Purpose:** {Why does the system use this API?}
|
||||
- **Base URL(s):**
|
||||
- Production: `{URL}`
|
||||
- Staging/Dev: `{URL}`
|
||||
- **Authentication:** {Describe method - e.g., API Key in Header (Header Name: `X-API-Key`), OAuth 2.0 Client Credentials, Basic Auth. Reference `docs/environment-vars.md` for key names.}
|
||||
- **Key Endpoints Used:**
|
||||
- **`{HTTP Method} {/path/to/endpoint}`:**
|
||||
- Description: {What does this endpoint do?}
|
||||
- Request Parameters: {Query params, path params}
|
||||
- Request Body Schema: {Provide JSON schema or link to `docs/data-models.md`}
|
||||
- Example Request: `{Code block}`
|
||||
- Success Response Schema (Code: `200 OK`): {JSON schema or link}
|
||||
- Error Response Schema(s) (Codes: `4xx`, `5xx`): {JSON schema or link}
|
||||
- Example Response: `{Code block}`
|
||||
- **`{HTTP Method} {/another/endpoint}`:** {...}
|
||||
- **Rate Limits:** {If known}
|
||||
- **Link to Official Docs:** {URL}
|
||||
|
||||
### {Another External Service Name} API
|
||||
|
||||
{...}
|
||||
|
||||
## Internal APIs Provided (If Applicable)
|
||||
|
||||
{If the system exposes its own APIs (e.g., in a microservices architecture or for a UI frontend). Repeat for each API.}
|
||||
|
||||
### {Internal API / Service Name} API
|
||||
|
||||
- **Purpose:** {What service does this API provide?}
|
||||
- **Base URL(s):** {e.g., `/api/v1/...`}
|
||||
- **Authentication/Authorization:** {Describe how access is controlled.}
|
||||
- **Endpoints:**
|
||||
- **`{HTTP Method} {/path/to/endpoint}`:**
|
||||
- Description: {What does this endpoint do?}
|
||||
- Request Parameters: {...}
|
||||
- Request Body Schema: {...}
|
||||
- Success Response Schema (Code: `200 OK`): {...}
|
||||
- Error Response Schema(s) (Codes: `4xx`, `5xx`): {...}
|
||||
- **`{HTTP Method} {/another/endpoint}`:** {...}
|
||||
|
||||
## AWS Service SDK Usage (or other Cloud Providers)
|
||||
|
||||
{Detail interactions with cloud provider services via SDKs.}
|
||||
|
||||
### {AWS Service Name, e.g., S3}
|
||||
|
||||
- **Purpose:** {Why is this service used?}
|
||||
- **SDK Package:** {e.g., `@aws-sdk/client-s3`}
|
||||
- **Key Operations Used:** {e.g., `GetObjectCommand`, `PutObjectCommand`}
|
||||
- Operation 1: {Brief description of usage context}
|
||||
- Operation 2: {...}
|
||||
- **Key Resource Identifiers:** {e.g., Bucket names, Table names - reference `docs/environment-vars.md`}
|
||||
|
||||
### {Another AWS Service Name, e.g., SES}
|
||||
|
||||
{...}
|
||||
|
||||
## 5. Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
```
|
||||
@@ -43,5 +43,4 @@
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------------------------ | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial epic definition | {Agent/Person} |
|
||||
| Refined Tech | YYYY-MM-DD | 0.2 | Added tech details (Story X.Y) | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
92
CURRENT-V2/gems-and-gpts/prd.txt
Normal file
92
CURRENT-V2/gems-and-gpts/prd.txt
Normal file
@@ -0,0 +1,92 @@
|
||||
{Format output as markdown that follows}
|
||||
|
||||
# {Project Name} Product Requirements Document (PRD)
|
||||
|
||||
## Intro
|
||||
|
||||
{Short 1-2 paragraph describing the what and why of the product/system being built for this version/MVP, referencing the provided project brief or user provided ideation.}
|
||||
|
||||
## Goals and Context
|
||||
|
||||
- **Project Objectives:** {Summarize the key business/user objectives this product/MVP aims to achieve. Refine goals from the Project Brief.}
|
||||
- **Measurable Outcomes:** {How will success be tangibly measured? Define specific outcomes.}
|
||||
- **Success Criteria:** {What conditions must be met for the MVP/release to be considered successful?}
|
||||
- **Key Performance Indicators (KPIs):** {List the specific metrics that will be tracked.}
|
||||
|
||||
## Scope and Requirements (MVP / Current Version)
|
||||
|
||||
### Functional Requirements (High-Level)
|
||||
|
||||
{List the major capabilities the system must have. Describe _what_ the system does, not _how_. Group related requirements.}
|
||||
|
||||
- Capability 1: ...
|
||||
- Capability 2: ...
|
||||
|
||||
### Non-Functional Requirements (NFRs)
|
||||
|
||||
{List key quality attributes and constraints.}
|
||||
|
||||
- **Performance:** {e.g., Response times, load capacity}
|
||||
- **Scalability:** {e.g., Ability to handle growth}
|
||||
- **Reliability/Availability:** {e.g., Uptime requirements, error handling expectations}
|
||||
- **Security:** {e.g., Authentication, authorization, data protection, compliance}
|
||||
- **Maintainability:** {e.g., Code quality standards, documentation needs}
|
||||
- **Usability/Accessibility:** {High-level goals; details in UI/UX Spec if applicable}
|
||||
- **Other Constraints:** {e.g., Technology constraints, budget, timeline}
|
||||
|
||||
### User Experience (UX) Requirements (High-Level)
|
||||
|
||||
{Describe the key aspects of the desired user experience. If a UI exists, create a placeholder markdown link to `docs/ui-ux-spec.md` for details.}
|
||||
|
||||
- UX Goal 1: ...
|
||||
- UX Goal 2: ...
|
||||
|
||||
### Integration Requirements (High-Level)
|
||||
|
||||
{List key external systems or services this product needs to interact with.}
|
||||
|
||||
- Integration Point 1: {e.g., Payment Gateway, External API X, Internal Service Y}
|
||||
- Integration Point 2: ...
|
||||
- _(See `docs/api-reference.md` for technical details)_
|
||||
|
||||
### Testing Requirements (High-Level)
|
||||
|
||||
{Briefly outline the overall expectation for testing - as the details will be in the testing strategy doc.}
|
||||
|
||||
- {e.g., "Comprehensive unit, integration, and E2E tests are required.", "Specific performance testing is needed for component X."}
|
||||
- _(See `docs/testing-strategy.md` for details)_
|
||||
|
||||
## Epic Overview (MVP / Current Version)
|
||||
|
||||
{List the major epics that break down the work for the MVP. Include a brief goal for each epic. Detailed stories reside in `docs/epicN.md` files.}
|
||||
|
||||
- **Epic 1: {Epic Title}** - Goal: {...}
|
||||
- **Epic 2: {Epic Title}** - Goal: {...}
|
||||
- **Epic N: {Epic Title}** - Goal: {...}
|
||||
|
||||
## Key Reference Documents
|
||||
|
||||
{Markdown Links to other relevant documents in the `docs/` folder that will be created.}
|
||||
|
||||
- `docs/project-brief.md`
|
||||
- `docs/architecture.md`
|
||||
- `docs/epic1.md`, `docs/epic2.md`, ...
|
||||
- `docs/tech-stack.md`
|
||||
- `docs/api-reference.md`
|
||||
- `docs/testing-strategy.md`
|
||||
- `docs/ui-ux-spec.md` (if applicable)
|
||||
- ... (other relevant docs)
|
||||
|
||||
## Post-MVP / Future Enhancements
|
||||
|
||||
{List ideas or planned features for future versions beyond the scope of the current PRD.}
|
||||
|
||||
- Idea 1: ...
|
||||
- Idea 2: ...
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ---------------------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft based on brief | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
36
CURRENT-V2/gems-and-gpts/project-brief.txt
Normal file
36
CURRENT-V2/gems-and-gpts/project-brief.txt
Normal file
@@ -0,0 +1,36 @@
|
||||
{Format output as markdown that follows}
|
||||
|
||||
# Project Brief: {Project Name}
|
||||
|
||||
## Introduction / Problem Statement
|
||||
|
||||
{Describe the core idea, the problem being solved, or the opportunity being addressed. Why is this project needed?}
|
||||
|
||||
## Vision & Goals
|
||||
|
||||
- **Vision:** {Describe the high-level desired future state or impact of this project.}
|
||||
- **Primary Goals:** {List 2-5 specific, measurable, achievable, relevant, time-bound (SMART) goals for the Minimum Viable Product (MVP).}
|
||||
- Goal 1: ...
|
||||
- Goal 2: ...
|
||||
- **Success Metrics (Initial Ideas):** {How will we measure if the project/MVP is successful? List potential KPIs.}
|
||||
|
||||
## Target Audience / Users
|
||||
|
||||
{Describe the primary users of this product/system. Who are they? What are their key characteristics or needs relevant to this project?}
|
||||
|
||||
## Key Features / Scope (High-Level Ideas for MVP)
|
||||
|
||||
{List the core functionalities or features envisioned for the MVP. Keep this high-level; details will go in the PRD/Epics.}
|
||||
|
||||
- Feature Idea 1: ...
|
||||
- Feature Idea 2: ...
|
||||
- Feature Idea N: ...
|
||||
|
||||
## Known Technical Constraints or Preferences
|
||||
|
||||
- **Constraints:** {List any known limitations and technical mandates or preferences - e.g., budget, timeline, specific technology mandates, required integrations, compliance needs.}
|
||||
- **Risks:** {Identify potential risks - e.g., technical challenges, resource availability, market acceptance, dependencies.}
|
||||
|
||||
## Relevant Research (Optional)
|
||||
|
||||
{Link to or summarize findings from any initial research conducted and referenced.}
|
||||
84
CURRENT-V2/gems-and-gpts/story-template.txt
Normal file
84
CURRENT-V2/gems-and-gpts/story-template.txt
Normal file
@@ -0,0 +1,84 @@
|
||||
# Story {EpicNum}.{StoryNum}: {Short Title Copied from Epic File}
|
||||
|
||||
**Status:** Draft | In-Progress | Complete
|
||||
|
||||
## Goal & Context
|
||||
|
||||
**User Story:** {As a [role], I want [action], so that [benefit] - Copied or derived from Epic file}
|
||||
|
||||
**Context:** {Briefly explain how this story fits into the Epic's goal and the overall workflow. Mention the previous story's outcome if relevant. Example: "This story builds upon the project setup (Story 1.1) by defining the S3 resource needed for state persistence..."}
|
||||
|
||||
## Detailed Requirements
|
||||
|
||||
{Copy the specific requirements/description for this story directly from the corresponding `docs/epicN.md` file.}
|
||||
|
||||
## Acceptance Criteria (ACs)
|
||||
|
||||
{Copy the Acceptance Criteria for this story directly from the corresponding `docs/epicN.md` file.}
|
||||
|
||||
- AC1: ...
|
||||
- AC2: ...
|
||||
- ACN: ...
|
||||
|
||||
## Technical Implementation Context
|
||||
|
||||
**Guidance:** Use the following details for implementation. Refer to the linked `docs/` files for broader context if needed.
|
||||
|
||||
- **Relevant Files:**
|
||||
|
||||
- Files to Create: {e.g., `src/services/s3-service.ts`, `test/unit/services/s3-service.test.ts`}
|
||||
- Files to Modify: {e.g., `lib/hacker-news-briefing-stack.ts`, `src/common/types.ts`}
|
||||
- _(Hint: See `docs/project-structure.md` for overall layout)_
|
||||
|
||||
- **Key Technologies:**
|
||||
|
||||
- {e.g., TypeScript, Node.js 22.x, AWS CDK (`aws-s3` construct), AWS SDK v3 (`@aws-sdk/client-s3`), Jest}
|
||||
- {If a UI story, mention specific frontend libraries/framework features (e.g., React Hooks, Vuex store, CSS Modules)}
|
||||
- _(Hint: See `docs/tech-stack.md` for full list)_
|
||||
|
||||
- **API Interactions / SDK Usage:**
|
||||
|
||||
- {e.g., "Use `@aws-sdk/client-s3`: `S3Client`, `GetObjectCommand`, `PutObjectCommand`.", "Handle `NoSuchKey` error specifically for `GetObjectCommand`."}
|
||||
- _(Hint: See `docs/api-reference.md` for details on external APIs and SDKs)_
|
||||
|
||||
- **UI/UX Notes:** ONLY IF THIS IS A UI Focused Epic or Story
|
||||
|
||||
- **Data Structures:**
|
||||
|
||||
- {e.g., "Define/Use `AppState` interface in `src/common/types.ts`: `{ processedStoryIds: string[] }`.", "Handle JSON parsing/stringifying for state."}
|
||||
- _(Hint: See `docs/data-models.md` for key project data structures)_
|
||||
|
||||
- **Environment Variables:**
|
||||
|
||||
- {e.g., `S3_BUCKET_NAME` (Read via `config.ts` or passed to CDK)}
|
||||
- _(Hint: See `docs/environment-vars.md` for all variables)_
|
||||
|
||||
- **Coding Standards Notes:**
|
||||
- {e.g., "Use `async/await` for all S3 calls.", "Implement error logging using `console.error`.", "Follow `kebab-case` for filenames, `PascalCase` for interfaces."}
|
||||
- _(Hint: See `docs/coding-standards.md` for full standards)_
|
||||
|
||||
## Tasks / Subtasks
|
||||
|
||||
{Copy the initial task breakdown from the corresponding `docs/epicN.md` file and expand or clarify as needed to ensure the agent can complete all AC. The agent can check these off as it proceeds.}
|
||||
|
||||
- [ ] Task 1
|
||||
- [ ] Task 2
|
||||
- [ ] Subtask 2.1
|
||||
- [ ] Task 3
|
||||
|
||||
## Testing Requirements
|
||||
|
||||
**Guidance:** Verify implementation against the ACs using the following tests.
|
||||
|
||||
- **Unit Tests:** {e.g., "Write unit tests for `src/services/s3-service.ts`. Mock `S3Client` and its commands (`GetObjectCommand`, `PutObjectCommand`). Test successful read/write, JSON parsing/stringifying, and `NoSuchKey` error handling."}
|
||||
- **Integration Tests:** {e.g., "No specific integration tests required for _just_ this story's module, but it will be covered later in `test/integration/fetch-flow.test.ts`."}
|
||||
- **Manual/CLI Verification:** {e.g., "Not applicable directly, but functionality tested via `npm run fetch-stories` later."}
|
||||
- _(Hint: See `docs/testing-strategy.md` for the overall approach)_
|
||||
|
||||
## Story Wrap Up (Agent Populates After Execution)
|
||||
|
||||
- **Agent Model Used:** `<Agent Model Name/Version>`
|
||||
- **Completion Notes:** {Any notes about implementation choices, difficulties, or follow-up needed}
|
||||
- **Change Log:** {Track changes _within this specific story file_ if iterations occur}
|
||||
- Initial Draft
|
||||
- ...
|
||||
99
CURRENT-V2/gems-and-gpts/ui-ux-spec.txt
Normal file
99
CURRENT-V2/gems-and-gpts/ui-ux-spec.txt
Normal file
@@ -0,0 +1,99 @@
|
||||
# {Project Name} UI/UX Specification
|
||||
|
||||
## Introduction
|
||||
|
||||
{State the purpose - to define the user experience goals, information architecture, user flows, and visual design specifications for the project's user interface.}
|
||||
|
||||
- **Link to Primary Design Files:** {e.g., Figma, Sketch, Adobe XD URL}
|
||||
- **Link to Deployed Storybook / Design System:** {URL, if applicable}
|
||||
|
||||
## Overall UX Goals & Principles
|
||||
|
||||
- **Target User Personas:** {Reference personas or briefly describe key user types and their goals.}
|
||||
- **Usability Goals:** {e.g., Ease of learning, efficiency of use, error prevention.}
|
||||
- **Design Principles:** {List 3-5 core principles guiding the UI/UX design - e.g., "Clarity over cleverness", "Consistency", "Provide feedback".}
|
||||
|
||||
## Information Architecture (IA)
|
||||
|
||||
- **Site Map / Screen Inventory:**
|
||||
```mermaid
|
||||
graph TD
|
||||
A[Homepage] --> B(Dashboard);
|
||||
A --> C{Settings};
|
||||
B --> D[View Details];
|
||||
C --> E[Profile Settings];
|
||||
C --> F[Notification Settings];
|
||||
```
|
||||
_(Or provide a list of all screens/pages)_
|
||||
- **Navigation Structure:** {Describe primary navigation (e.g., top bar, sidebar), secondary navigation, breadcrumbs, etc.}
|
||||
|
||||
## User Flows
|
||||
|
||||
{Detail key user tasks. Use diagrams or descriptions.}
|
||||
|
||||
### {User Flow Name, e.g., User Login}
|
||||
|
||||
- **Goal:** {What the user wants to achieve.}
|
||||
- **Steps / Diagram:**
|
||||
```mermaid
|
||||
graph TD
|
||||
Start --> EnterCredentials[Enter Email/Password];
|
||||
EnterCredentials --> ClickLogin[Click Login Button];
|
||||
ClickLogin --> CheckAuth{Auth OK?};
|
||||
CheckAuth -- Yes --> Dashboard;
|
||||
CheckAuth -- No --> ShowError[Show Error Message];
|
||||
ShowError --> EnterCredentials;
|
||||
```
|
||||
_(Or: Link to specific flow diagram in Figma/Miro)_
|
||||
|
||||
### {Another User Flow Name}
|
||||
|
||||
{...}
|
||||
|
||||
## Wireframes & Mockups
|
||||
|
||||
{Reference the main design file link above. Optionally embed key mockups or describe main screen layouts.}
|
||||
|
||||
- **Screen / View Name 1:** {Description of layout and key elements. Link to specific Figma frame/page.}
|
||||
- **Screen / View Name 2:** {...}
|
||||
|
||||
## Component Library / Design System Reference
|
||||
|
||||
{Link to the primary source (Storybook, Figma Library). If none exists, define key components here.}
|
||||
|
||||
### {Component Name, e.g., Primary Button}
|
||||
|
||||
- **Appearance:** {Reference mockup or describe styles.}
|
||||
- **States:** {Default, Hover, Active, Disabled, Loading.}
|
||||
- **Behavior:** {Interaction details.}
|
||||
|
||||
### {Another Component Name}
|
||||
|
||||
{...}
|
||||
|
||||
## Branding & Style Guide Reference
|
||||
|
||||
{Link to the primary source or define key elements here.}
|
||||
|
||||
- **Color Palette:** {Primary, Secondary, Accent, Feedback colors (hex codes).}
|
||||
- **Typography:** {Font families, sizes, weights for headings, body, etc.}
|
||||
- **Iconography:** {Link to icon set, usage notes.}
|
||||
- **Spacing & Grid:** {Define margins, padding, grid system rules.}
|
||||
|
||||
## Accessibility (AX) Requirements
|
||||
|
||||
- **Target Compliance:** {e.g., WCAG 2.1 AA}
|
||||
- **Specific Requirements:** {Keyboard navigation patterns, ARIA landmarks/attributes for complex components, color contrast minimums.}
|
||||
|
||||
## Responsiveness
|
||||
|
||||
- **Breakpoints:** {Define pixel values for mobile, tablet, desktop, etc.}
|
||||
- **Adaptation Strategy:** {Describe how layout and components adapt across breakpoints. Reference designs.}
|
||||
|
||||
## Change Log
|
||||
|
||||
| Change | Date | Version | Description | Author |
|
||||
| ------------- | ---------- | ------- | ------------------- | -------------- |
|
||||
| Initial draft | YYYY-MM-DD | 0.1 | Initial draft | {Agent/Person} |
|
||||
| Added Flow X | YYYY-MM-DD | 0.2 | Defined user flow X | {Agent/Person} |
|
||||
| ... | ... | ... | ... | ... |
|
||||
17
README.md
17
README.md
@@ -10,6 +10,7 @@ The BMad Method has undergone a significant transformation with our V2 (beta) re
|
||||
- **Standardized Templates**: Comprehensive set of templates for consistent document creation
|
||||
- **Streamlined Workflow**: Clearer process from idea to deployment
|
||||
- **Improved Agile Integration**: Better support for agile methodologies
|
||||
- **Agent vs Gem Agent Distinction**: V2 has specific [gems](#custom-gems-and-gpts) (agent with embedded templates) in parity with the IDE agents.
|
||||
|
||||
## No Rules Required!
|
||||
|
||||
@@ -102,7 +103,7 @@ Join the [Community Discussion Forum](https://github.com/bmadcode/BMAD-METHOD/di
|
||||
|
||||
## Template Dependencies
|
||||
|
||||
**Important:** The agents in this system rely on template files located in the `CURRENT-V2/docs/templates` folder. These templates should remain named as they are for proper functionality, including:
|
||||
**Important:** The agents (not gems) in this system rely on template files located in the `CURRENT-V2/docs/templates` folder. These templates should remain named as they are for proper functionality and put in your projects docs/templates folder, including:
|
||||
|
||||
- `architecture.md`
|
||||
- `story-template.md`
|
||||
@@ -110,19 +111,11 @@ Join the [Community Discussion Forum](https://github.com/bmadcode/BMAD-METHOD/di
|
||||
- `project-brief.md`
|
||||
- And more specific templates for various document types
|
||||
|
||||
## Using Agents with Web-Based AI Interfaces (Highly recommended, save lots of money, larger context windows, deep research is a game changer)
|
||||
## Custom GEMs and GPTs
|
||||
|
||||
If you plan to use the agents in web interfaces like Gemini Web or OpenAI Web, we recommend:
|
||||
**Using Agents with Web-Based AI Interfaces (Highly recommended, save lots of money, larger context windows, deep research is a game changer)**
|
||||
|
||||
1. For Analyst, Architect, PM/PO, and SM agents:
|
||||
|
||||
- Either paste the templates into your web session
|
||||
- Or modify the agent prompt to include the template as an addendum
|
||||
- Change file paths references to point to the document itself rather than external files
|
||||
|
||||
2. Implementation approaches:
|
||||
- **Recommended:** Add the template content directly into the prompt as an addendum
|
||||
- Reference the template in the document rather than as an external file
|
||||
The [gems folder](./CURRENT-V2/gems-and-gpts/) contains agent instructions embedded with optimized web use instructions - streamlined for usage within the [Gemini Gems](https://gemini.google.com/gems/create), or [OpenAIs custom GPT's](https://chatgpt.com/gpts/editor). With both custom GPTs and Gemini Gems, you will attach the templates now instead of embedding them (as was the case with V1 of this system, that was not as easy to modify). This way, as you modify templates from the templates folder, if you want to change it in the web version just save it as a .txt extension and attach to the custom GEM or GPT.
|
||||
|
||||
## Getting Started
|
||||
|
||||
|
||||
Reference in New Issue
Block a user