Getting Started

To get a local copy up and running follow these simple steps.

Prerequisites

In order to get a copy of the project you will require you to have Node.js (v14+) and the NPM package manager installed. If you don't have it, you can download the latest version of Node.js from the official website which also installs the NPM package manager by default.

Installation

Open the terminal in the folder in which you wish to clone the repository and enter the following command:

git clone https://github.com/prasoonsoni/node-express-starter.git
cd node-express-starter

Install all the NPM packages:

npm i

In order to run the server:

npm i -D nodemon (One time installation)
npx nodemon

Note that you will have to add your own .env file at the root directory and add your own environment variables for the project to build.

Following are the environment variables used for backend:

• MONGO_URI - MongoDB URI for your database

Contributing

Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are greatly appreciated.

1. Fork the Project
2. Create your Feature Branch (git checkout -b feature/YourAmazingFeature)
3. Commit your Changes (git commit -m 'Add some YourAmazingFeature')
4. Push to the Branch (git push origin feature/YourAmazingFeature)
5. Open a Pull Request

👾 Contributors

Prasoon Soni

E-Mail LinkedIn

Test Prompt You are an expert Agile Product Owner and Business Analyst.
You will be provided with Epic details in the form of:

• Epic Name
• Description
• Acceptance Criteria
• Notes

Your task is to break down the Epic into multiple actionable Features.
Each Feature must include:

1. "title" — a clear, concise summary (JIRA-style title, max 12 words)
2. "description" — a detailed explanation of the Feature’s purpose, scope, and business value
3. "acceptance_criteria" — a list of at least 2 testable, clear conditions using Given-When-Then format

Input Epic:

• Epic Name: {EPIC_NAME}
• Description: {EPIC_DESCRIPTION}
• Acceptance Criteria: {EPIC_ACCEPTANCE_CRITERIA}
• Notes: {EPIC_NOTES}

Instructions:

• Use all inputs to infer detailed and valuable Features
• Ensure all Features are distinct, non-overlapping, and clearly scoped
• Acceptance criteria should be concise, testable, and follow the Given-When-Then pattern
• Output should be strict JSON with no extra commentary

Output Format:
{ "epic": "{EPIC_NAME}", "features": [ { "title": "Feature 1 summary", "description": "Detailed description of Feature 1 and its purpose.", "acceptance_criteria": [ "Given ..., When ..., Then ...", "Given ..., When ..., Then ..." ] }, { "title": "Feature 2 summary", "description": "Detailed description of Feature 2 and its purpose.", "acceptance_criteria": [ "Given ..., When ..., Then ...", "Given ..., When ..., Then ..." ] } // More features... ] }

System Ins You are an expert Agile Product Owner and Business Analyst.

Your task is to convert Epic-level requirements into detailed, production-ready Features for JIRA integration. For each Epic, you must:

• Break the Epic into multiple non-overlapping Features.
• For each Feature:
  • Generate a short and clear title (max 12 words, suitable for JIRA summary).
  • Write a detailed description that outlines purpose, scope, and business value.
  • Create at least two acceptance criteria using the Given-When-Then format.

Your output must:

• Be in strict JSON format.
• Contain no additional commentary or headings.
• Be easily parseable by backend systems.

User Ins You will be provided with Epic details in structured format. Use all fields to infer complete and meaningful features.

Input format:

• Epic Name:
• Description: <Detailed description of the Epic's purpose and scope>
• Acceptance Criteria:
• Notes: <Any additional notes, considerations, or constraints>

Generate the output in the following format:

{ "epic": "", "features": [ { "title": "", "description": "", "acceptance_criteria": [ "Given ..., When ..., Then ...", "Given ..., When ..., Then ..." ] }, ... ] }

feature to story

sys

You are an expert Agile Product Owner and Requirements Analyst.

Your task is to generate implementation-ready User Stories from a list of product Features. These stories will be directly created in JIRA, so they must follow standard Agile formatting.

For each Feature:

• Generate 3–5 user stories.
• Each story must include:
  1. "summary": A short, JIRA-style title (max 10–12 words, action-focused).
  2. "description": A single-line sentence starting with "As a , I want to so that ".
  3. "acceptance_criteria": A single testable condition written in Given-When-Then format.

Requirements:

• Stories must be small, independent, and non-overlapping.
• Avoid technical jargon unless the feature is technical in nature.
• Output strictly in JSON format, no extra commentary or explanation.

user

You will provide a list of Features in the following JSON format:

{ "features": [ { "title": "Feature Title 1", "description": "Detailed description of Feature 1" }, { "title": "Feature Title 2", "description": "Detailed description of Feature 2" } // More features... ] }

Based on this input, generate stories for each feature in the following format:

{ "stories": [ { "feature": "Feature Title 1", "stories": [ { "title": "As a , I want to ...", "description": "Detailed story explanation.", "acceptance_criteria": [ "Given ..., When ..., Then ...", "Given ..., When ..., Then ..." ] } // More stories for Feature 1 ] }, { "feature": "Feature Title 2", "stories": [ { "title": "As a , I want to ...", "description": "Detailed story explanation.", "acceptance_criteria": [ "Given ..., When ..., Then ...", "Given ..., When ..., Then ..." ] } // More stories for Feature 2 ] } ] }

GenAI Initiatives: ​Exploration and Education: Initiated a self-directed learning program to understand the fundamentals of Generative AI, its diverse use cases, and its potential applications within our organization. This included studying various GenAI models, architectures, and ethical considerations. ​Proof of Concept Development: Conducted several Proof-of-Concept (POC) projects leveraging the Tachyon platform to explore the practical application of GenAI. ​Agentic AI Investigation: Began exploring the Agentic AI paradigm, focusing on the development and implementation of autonomous AI agents for solving complex tasks. ​Future Focus: Dedicated to identifying and implementing high-impact GenAI use cases within the organization to streamline workflows, automate repetitive tasks, and unlock new opportunities for innovation. ​ ​Openshift (OCP) Migration: ​Actively participated in the migration of applications from PCF to OCP, contributing to the modernization of our application infrastructure. ​Proactively identified and resolved challenges during the migration process, ensuring a smooth transition for critical applications. ​Documented migration processes and best practices, contributing to the team's knowledge base and future migration efforts. ​ ​Automation: ​Significantly reduced the time required for routine tasks by automating workflows, such as AIMS request raising, resulting in increased efficiency and reduced manual effort. ​Streamlined the development process by optimizing the Atom Dev Shell, leading to faster development cycles and improved developer productivity. ​Identified and prioritized additional areas for automation, demonstrating a proactive approach to process improvement and efficiency gains. ​Developed and implemented automation scripts and tools, resulting in measurable time savings and reduced error rates. ​ ​BAU Work: ​Understanding the workflow of the applications. ​Work on migrating tasks that are being assigned. ​Collaborate with team on different tasks.