Spaces:
Sleeping
Sleeping
Commit
·
01468b6
1
Parent(s):
01981b2
Refactor proposal template and instructions for improved clarity and structure
Browse files- custom-gpt-action.yaml +176 -23
- instructions.md +75 -32
- src/proposal_template.md +2 -9
custom-gpt-action.yaml
CHANGED
|
@@ -16,9 +16,9 @@ paths:
|
|
| 16 |
content:
|
| 17 |
application/json:
|
| 18 |
schema:
|
| 19 |
-
$ref:
|
| 20 |
responses:
|
| 21 |
-
|
| 22 |
description: Successfully generated proposal
|
| 23 |
content:
|
| 24 |
application/json:
|
|
@@ -27,8 +27,8 @@ paths:
|
|
| 27 |
properties:
|
| 28 |
proposal:
|
| 29 |
type: string
|
| 30 |
-
example:
|
| 31 |
-
|
| 32 |
description: Internal server error
|
| 33 |
content:
|
| 34 |
application/json:
|
|
@@ -37,7 +37,7 @@ paths:
|
|
| 37 |
properties:
|
| 38 |
detail:
|
| 39 |
type: string
|
| 40 |
-
example:
|
| 41 |
components:
|
| 42 |
schemas:
|
| 43 |
ProposalRequest:
|
|
@@ -60,50 +60,203 @@ components:
|
|
| 60 |
properties:
|
| 61 |
project_name:
|
| 62 |
type: string
|
| 63 |
-
description:
|
|
|
|
| 64 |
project_overview:
|
| 65 |
type: string
|
| 66 |
-
description:
|
|
|
|
|
|
|
| 67 |
project_introduction:
|
| 68 |
type: string
|
| 69 |
-
description:
|
|
|
|
|
|
|
| 70 |
about_us:
|
| 71 |
type: string
|
| 72 |
description: "Provide a short introduction to Sifars, focusing on our team's expertise, technologies, and successful solutions we have developed. Mention how long Sifars has been in operation and our experience with similar projects."
|
|
|
|
|
|
|
| 73 |
background_of_the_project:
|
| 74 |
type: string
|
| 75 |
description: "Describe the key challenge the client is facing in their industry (replace with the client's field, e.g., healthcare, finance). Present the problem and how Sifars will address it using advanced technologies (AI, software development, automation, etc.)."
|
|
|
|
|
|
|
| 76 |
scope_of_work:
|
| 77 |
type: string
|
| 78 |
-
description:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 79 |
technical_approach:
|
| 80 |
type: string
|
| 81 |
description: "Explain the approach in detail. Include methodologies like content-based and collaborative filtering if relevant, or other techniques used by Sifars. Customize this to reflect the [Techstack] that's going to be used by Sifars."
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 82 |
deployment_and_integration:
|
| 83 |
type: string
|
| 84 |
-
description:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 85 |
timeline:
|
| 86 |
-
|
| 87 |
-
|
| 88 |
-
|
| 89 |
-
|
| 90 |
-
|
| 91 |
-
|
| 92 |
-
|
| 93 |
-
|
| 94 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 95 |
team_structure:
|
| 96 |
type: string
|
| 97 |
description: "Generate a detailed breakdown of a project team's structure, including roles and responsibilities. The team may consist of members like Project Manager, UI/UX Designer, Full Stack Developers, AI Developers, Quality Assurance Specialists, DevOps Engineers, etc. For each role, provide the number of members and describe their key responsibilities. Ensure that the responsibilities align with typical tasks for each role in a software development project. Use clear, professional language and ensure that the descriptions are concise yet comprehensive."
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 98 |
platform:
|
| 99 |
type: string
|
| 100 |
-
description:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 101 |
licensing_model:
|
| 102 |
type: string
|
| 103 |
-
description:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 104 |
risk_analysis:
|
| 105 |
type: string
|
| 106 |
-
description:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 107 |
past_projects:
|
| 108 |
type: string
|
| 109 |
-
description:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 16 |
content:
|
| 17 |
application/json:
|
| 18 |
schema:
|
| 19 |
+
$ref: '#/components/schemas/ProposalRequest'
|
| 20 |
responses:
|
| 21 |
+
'200':
|
| 22 |
description: Successfully generated proposal
|
| 23 |
content:
|
| 24 |
application/json:
|
|
|
|
| 27 |
properties:
|
| 28 |
proposal:
|
| 29 |
type: string
|
| 30 |
+
example: 'Generated proposal content here.'
|
| 31 |
+
'500':
|
| 32 |
description: Internal server error
|
| 33 |
content:
|
| 34 |
application/json:
|
|
|
|
| 37 |
properties:
|
| 38 |
detail:
|
| 39 |
type: string
|
| 40 |
+
example: 'Internal Server Error.'
|
| 41 |
components:
|
| 42 |
schemas:
|
| 43 |
ProposalRequest:
|
|
|
|
| 60 |
properties:
|
| 61 |
project_name:
|
| 62 |
type: string
|
| 63 |
+
description: 'Generate a name of the project. In response, provide only the name and do not include any other information.'
|
| 64 |
+
example: 'MyCares'
|
| 65 |
project_overview:
|
| 66 |
type: string
|
| 67 |
+
description: 'Generate an overview section that improves the project overview from the client requirements. Keep the text up to 15 lines and write the text without using pronouns.'
|
| 68 |
+
example: |
|
| 69 |
+
The **MyCares** application aims to offer a comprehensive digital platform catering to health management, social engagement, and spiritual well-being. Key features include user authentication, health tracking, group management, reminders, and AI-based image analysis. Integrating advanced AI and cloud technologies, the application will revolutionize personal health tracking and social connectivity in one unified platform.
|
| 70 |
project_introduction:
|
| 71 |
type: string
|
| 72 |
+
description: 'Address the client formally and thank them for considering Sifars for the project. Briefly describe Sifars, mentioning its mission, values, and focus on delivering state-of-the-art AI or software solutions.'
|
| 73 |
+
example: |
|
| 74 |
+
Thank you for considering Sifars as your technology partner for the development of the **MyCares** application. At Sifars, we are committed to delivering cutting-edge AI and software solutions that drive innovation and transform businesses. Our team of experts is dedicated to providing exceptional service and ensuring the success of every project we undertake.
|
| 75 |
about_us:
|
| 76 |
type: string
|
| 77 |
description: "Provide a short introduction to Sifars, focusing on our team's expertise, technologies, and successful solutions we have developed. Mention how long Sifars has been in operation and our experience with similar projects."
|
| 78 |
+
example: |
|
| 79 |
+
Sifars is pleased to present a comprehensive proposal for the development and implementation of the **MyCares** application. As a leading provider of innovative software solutions, Sifars brings a wealth of experience and expertise to this project. With a proven track record of delivering tailored solutions that address our clients' unique needs, we are confident in our ability to successfully execute this project and exceed expectations.
|
| 80 |
background_of_the_project:
|
| 81 |
type: string
|
| 82 |
description: "Describe the key challenge the client is facing in their industry (replace with the client's field, e.g., healthcare, finance). Present the problem and how Sifars will address it using advanced technologies (AI, software development, automation, etc.)."
|
| 83 |
+
example: |
|
| 84 |
+
The **MyCares** application addresses a critical need in the healthcare industry by providing a comprehensive platform for health management, social engagement, and spiritual well-being. With the increasing demand for personalized health solutions and the rise of digital health technologies, there is a growing need for innovative applications that empower users to take control of their well-being. Sifars is uniquely positioned to develop the **MyCares** application, leveraging advanced AI and cloud technologies to deliver a cutting-edge solution that meets the evolving needs of the healthcare sector.
|
| 85 |
scope_of_work:
|
| 86 |
type: string
|
| 87 |
+
description: 'Detail the tasks that will be performed. Example structure: Data Collection and Preprocessing, Solution Development (e.g., AI model, software system), Integration and API development, Testing and validation, Deployment on scalable infrastructure.'
|
| 88 |
+
example: |
|
| 89 |
+
The scope of work for the **MyCares** application encompasses a range of tasks that will be executed with precision and expertise. The key components of the project include:
|
| 90 |
+
1. Data Collection and Preprocessing:
|
| 91 |
+
- Gathering relevant health data, user profiles, and social interaction metrics.
|
| 92 |
+
- Cleaning, structuring, and preparing the data for AI model training and analysis.
|
| 93 |
+
2. Solution Development:
|
| 94 |
+
- Designing and developing the core features of the application, including user authentication, health tracking, group management, and reminders.
|
| 95 |
+
- Implementing AI-based image analysis for medicine identification, food image recognition, and nutrition estimation.
|
| 96 |
+
3. Integration and API Development:
|
| 97 |
+
- Integrating third-party APIs for wearable device data, social media interactions, and cloud services.
|
| 98 |
+
- Developing custom APIs for seamless data exchange and communication between application components.
|
| 99 |
+
4. Testing and Validation:
|
| 100 |
+
- Conducting rigorous testing to ensure the application's functionality, performance, and security.
|
| 101 |
+
- Validating AI models for accuracy, reliability, and scalability.
|
| 102 |
+
5. Deployment on Scalable Infrastructure:
|
| 103 |
+
- Deploying the application on cloud infrastructure for scalability, reliability, and performance.
|
| 104 |
+
- Ensuring seamless integration with client platforms and services.
|
| 105 |
technical_approach:
|
| 106 |
type: string
|
| 107 |
description: "Explain the approach in detail. Include methodologies like content-based and collaborative filtering if relevant, or other techniques used by Sifars. Customize this to reflect the [Techstack] that's going to be used by Sifars."
|
| 108 |
+
example: |
|
| 109 |
+
Sifars will adopt a comprehensive technical approach to develop the **MyCares** application, leveraging cutting-edge technologies and best practices to deliver a robust and user-friendly platform. The key components of our technical approach include:
|
| 110 |
+
1. Agile Development Methodology:
|
| 111 |
+
- Following an agile development process to ensure flexibility, transparency, and client involvement throughout the project lifecycle.
|
| 112 |
+
- Conducting regular sprints, reviews, and retrospectives to maintain project momentum and address evolving requirements.
|
| 113 |
+
2. AI-Powered Features:
|
| 114 |
+
- Implementing AI models for image analysis, personalized recommendations, and health insights.
|
| 115 |
+
- Leveraging machine learning algorithms for data processing, pattern recognition, and predictive analytics.
|
| 116 |
+
3. Cloud Infrastructure:
|
| 117 |
+
- Deploying the application on cloud services for scalability, reliability, and performance.
|
| 118 |
+
- Utilizing serverless architecture, microservices, and containerization for efficient resource management.
|
| 119 |
+
4. Secure Development Practices:
|
| 120 |
+
- Following industry best practices for secure coding, data encryption, and access control.
|
| 121 |
+
- Conducting regular security audits, vulnerability assessments, and penetration testing to ensure data protection and compliance.
|
| 122 |
+
5. Continuous Integration and Deployment:
|
| 123 |
+
- Implementing CI/CD pipelines for automated testing, build, and deployment processes.
|
| 124 |
+
- Ensuring rapid iteration, feedback, and delivery of new features and updates.
|
| 125 |
deployment_and_integration:
|
| 126 |
type: string
|
| 127 |
+
description: 'Specify the deployment method, such as using cloud services like AWS, GCP, or any other infrastructure that Sifars uses or defined in the [Techstack]. Mention how Sifars ensures seamless integration with the client’s platform using APIs.'
|
| 128 |
+
example: |
|
| 129 |
+
The **MyCares** application will be deployed on cloud infrastructure to ensure scalability, reliability, and performance. Sifars will leverage Azure services for hosting, databases, and analytics, providing a secure and efficient environment for the application. The deployment process will involve:
|
| 130 |
+
1. Setting up virtual machine instances for the application backend and frontend.
|
| 131 |
+
2. Configuring databases for storing user profiles, health data, and interaction logs.
|
| 132 |
+
3. Implementing CI/CD pipelines for automated testing, build, and deployment.
|
| 133 |
+
4. Monitoring system performance, availability, and security using Azure tools.
|
| 134 |
+
5. Integrating third-party APIs for wearable device data, social media interactions, and cloud services.
|
| 135 |
+
|
| 136 |
+
Sifars will ensure seamless integration with the client's platform through custom APIs and data exchange mechanisms. By following industry best practices and standards, we will deliver a secure, reliable, and user-friendly application that meets the client's requirements and exceeds expectations. The integration process will be transparent, efficient, and collaborative, ensuring a smooth transition and successful deployment.
|
| 137 |
timeline:
|
| 138 |
+
type: string
|
| 139 |
+
description: 'Create a timeline with project milestones in the markdown table format. Add estimated pricing in a flexible structure, allowing payments at each milestone.'
|
| 140 |
+
example: |
|
| 141 |
+
The successful implementation of the **MyCares** will follow a structured timeline, ensuring timely delivery of milestones and alignment with project objectives. Below is the proposed timeline outlining key milestones and their respective durations:
|
| 142 |
+
|
| 143 |
+
| S. No. | Milestone | Efforts (Man Days) | Time (Days) | Price (USD) |
|
| 144 |
+
|--------|----------------------------|--------------------|-------------|-------------|
|
| 145 |
+
| 1 | High-Level Design Document | | | |
|
| 146 |
+
| 2 | Low-Level Design Document | | | |
|
| 147 |
+
| 3 | Milestone 1 | | | |
|
| 148 |
+
| 4 | Milestone 2 | | | |
|
| 149 |
+
| 5 | Milestone 3 | | | |
|
| 150 |
+
| 6 | Milestone 4 | | | |
|
| 151 |
+
| Total | | | | |
|
| 152 |
+
|
| 153 |
+
Note: Each Milestone will be of 2 weeks.
|
| 154 |
+
|
| 155 |
+
Efforts (Man Days): The number of days it will take for a single person todeliver the milestone, with a working day consisting of 8 hours.
|
| 156 |
+
Time (Days):The duration required for our team to deliver the milestone,considering a working day of 8 hours and involving multiple team members.
|
| 157 |
team_structure:
|
| 158 |
type: string
|
| 159 |
description: "Generate a detailed breakdown of a project team's structure, including roles and responsibilities. The team may consist of members like Project Manager, UI/UX Designer, Full Stack Developers, AI Developers, Quality Assurance Specialists, DevOps Engineers, etc. For each role, provide the number of members and describe their key responsibilities. Ensure that the responsibilities align with typical tasks for each role in a software development project. Use clear, professional language and ensure that the descriptions are concise yet comprehensive."
|
| 160 |
+
example: |
|
| 161 |
+
Project Manager (x1):
|
| 162 |
+
- Responsibilities:
|
| 163 |
+
- Overall project management and coordination.
|
| 164 |
+
- Stakeholder communication and client interaction.
|
| 165 |
+
- Planning and scheduling of tasks and milestones.
|
| 166 |
+
- Risk management and issue resolution.
|
| 167 |
+
- Ensuring project delivery within scope, schedule, and budget constraints.
|
| 168 |
+
UI/UX Designer (x1):
|
| 169 |
+
- Responsibilities:
|
| 170 |
+
- Designing user interfaces and user experiences.
|
| 171 |
+
- Creating wireframes, prototypes, and mockups.
|
| 172 |
+
- Conducting user research and usability testing.
|
| 173 |
+
- Collaborating with developers to ensure design feasibility.
|
| 174 |
+
Full Stack Developer (x2):
|
| 175 |
+
- Responsibilities:
|
| 176 |
+
- Developing front-end and back-end components.
|
| 177 |
+
- Integrating APIs and third-party services.
|
| 178 |
+
- Writing clean, maintainable, and efficient code.
|
| 179 |
+
- Conducting code reviews and ensuring code quality.
|
| 180 |
+
AI Developer (x1):
|
| 181 |
+
- Responsibilities:
|
| 182 |
+
- Developing and implementing AI models and algorithms.
|
| 183 |
+
- Data preprocessing and feature engineering.
|
| 184 |
+
- Model training, evaluation, and optimization.
|
| 185 |
+
- Collaborating with other developers for integration.
|
| 186 |
+
Quality Assurance Specialist (x1):
|
| 187 |
+
- Responsibilities:
|
| 188 |
+
- Creating and executing test plans and test cases.
|
| 189 |
+
- Identifying and reporting bugs and issues.
|
| 190 |
+
- Ensuring software quality and performance.
|
| 191 |
+
- Collaborating with developers to resolve issues.
|
| 192 |
+
DevOps Engineer (x1):
|
| 193 |
+
- Responsibilities:
|
| 194 |
+
- Managing deployment pipelines and CI/CD processes.
|
| 195 |
+
- Ensuring infrastructure scalability and reliability.
|
| 196 |
+
- Monitoring system performance and availability.
|
| 197 |
+
- Automating repetitive tasks and processes.
|
| 198 |
platform:
|
| 199 |
type: string
|
| 200 |
+
description: 'Generate text explaining each [Techstack] the application will be built upon.'
|
| 201 |
+
example: |
|
| 202 |
+
The **MyCares** application will be built upon a modern and robust technology stack, ensuring performance, scalability, and user satisfaction.
|
| 203 |
+
1. Frontend: React Native
|
| 204 |
+
- A flexible framework for developing cross-platform mobile applications for iOS and Android.
|
| 205 |
+
- Ensures a responsive, intuitive, and high-performing user interface.
|
| 206 |
+
- Allows for seamless integration with backend services and APIs.
|
| 207 |
+
2. Backend: Node.js
|
| 208 |
+
- A scalable and efficient backend platform ideal for real-time data handling and API integrations.
|
| 209 |
+
- Provides a robust environment for managing the application's core functionalities.
|
| 210 |
+
3. AI Engine: OpenAI
|
| 211 |
+
- Powers the application's AI capabilities, including image recognition and personalized recommendations.
|
| 212 |
+
- Enables features such as medicine identification, food image analysis, and nutrition estimation.
|
| 213 |
+
4. Cloud Infrastructure: Azure
|
| 214 |
+
- Secure and scalable hosting for application deployment.
|
| 215 |
+
- Facilitates CI/CD pipelines, data management, and reliable uptime.
|
| 216 |
+
- Provides robust monitoring and analytics tools.
|
| 217 |
+
5. Database: SQL
|
| 218 |
+
- Ensures secure storage of user profiles, health data, group interactions, and event logs.
|
| 219 |
+
- Offers high availability and quick data retrieval for a seamless user experience.
|
| 220 |
licensing_model:
|
| 221 |
type: string
|
| 222 |
+
description: 'Based on the [Techstack] and other potential tooling that will be involved to build the project, generate the Licensing Model section.'
|
| 223 |
+
example: |
|
| 224 |
+
The licensing model for the **MyCares** application will align with the chosen tech stack and any additional tools utilized during development. Below are the licensing considerations:
|
| 225 |
+
1. Frontend and Backend Development:
|
| 226 |
+
- React Native and Node.js are open-source frameworks, ensuring no licensing costs for these components.
|
| 227 |
+
- Adherence to MIT and other relevant licenses.
|
| 228 |
+
2. AI Integration:
|
| 229 |
+
- The AI modules leveraging OpenAI may incur licensing fees based on API usage. These costs will be calculated based on the volume of requests and are factored into the operational expenses.
|
| 230 |
+
3. Cloud Services:
|
| 231 |
+
- Azure services, including hosting, databases, and analytics, will require a subscription-based model. Licensing costs are determined by resource usage, such as virtual machine instances and data storage.
|
| 232 |
+
4. Third-Party APIs:
|
| 233 |
+
- Any third-party integrations, such as wearable device SDKs, may involve additional licensing agreements and fees. These will be transparently communicated during implementation. Note: Wearables are not covered in this phase though is expected to be covered in the immediate next phase (P2).
|
| 234 |
+
5. Ongoing Maintenance and Support:
|
| 235 |
+
- Post-deployment updates, AI model enhancements, and additional features may require separate licensing agreements or subscription renewals. The licensing model ensures compliance with all relevant agreements while maintaining cost transparency for long-term sustainability.
|
| 236 |
risk_analysis:
|
| 237 |
type: string
|
| 238 |
+
description: 'List potential risks (e.g., data availability, bias in the system) and propose mitigations.'
|
| 239 |
+
example: |
|
| 240 |
+
The **MyCares** project involves several risks that could impact project success and delivery. To address these risks, Sifars has developed a comprehensive risk analysis and mitigation plan, focusing on the following key areas:
|
| 241 |
+
1. Data Security and Privacy:
|
| 242 |
+
- Risk: Unauthorized access to sensitive user data, leading to privacy breaches and legal implications.
|
| 243 |
+
- Mitigation: Implement robust data encryption, access controls, and user authentication mechanisms to safeguard data integrity and confidentiality.
|
| 244 |
+
2. AI Model Performance:
|
| 245 |
+
- Risk: Inaccurate predictions, biased recommendations, or model drift affecting user experience and application functionality.
|
| 246 |
+
- Mitigation: Conduct rigorous testing, validation, and monitoring of AI models to ensure accuracy, fairness, and reliability. Implement feedback loops and model retraining to address performance issues.
|
| 247 |
+
3. Integration Challenges:
|
| 248 |
+
- Risk: Incompatibility with third-party APIs, data exchange issues, or deployment bottlenecks impacting system functionality.
|
| 249 |
+
- Mitigation: Conduct thorough API compatibility checks, data validation, and integration testing to identify and resolve issues early in the development process. Collaborate closely with third-party providers to ensure seamless integration and data exchange.
|
| 250 |
+
4. Scalability and Performance:
|
| 251 |
+
- Risk: System overload, slow response times, or downtime due to increased user traffic or data volume.
|
| 252 |
+
- Mitigation: Design the application for scalability, performance optimization, and load balancing to handle peak loads and ensure uninterrupted service. Implement monitoring tools and performance metrics to proactively address bottlenecks and optimize resource utilization.
|
| 253 |
+
5. Regulatory Compliance:
|
| 254 |
+
- Risk: Non-compliance with data protection regulations, industry standards, or ethical guidelines impacting legal liability and reputation.
|
| 255 |
+
- Mitigation: Stay informed of regulatory requirements, industry best practices, and ethical guidelines related to data privacy, AI ethics, and software development. Implement compliance checks, audits, and documentation processes to ensure adherence to relevant laws and standards.
|
| 256 |
past_projects:
|
| 257 |
type: string
|
| 258 |
+
description: 'Provide case studies of similar projects Sifars has worked on, showcasing the impact and results achieved. Refer to the knowledge files to find 2 relevant projects that could be similar to the provided requirements.'
|
| 259 |
+
example: |
|
| 260 |
+
Sifars has a proven track record of delivering innovative software solutions that drive business growth and transformation. Two projects that align closely with the requirements of the **MyCares** application are:
|
| 261 |
+
1. HealthTrack: A comprehensive health management platform that integrates AI-based health tracking, personalized recommendations, and social engagement features. HealthTrack has successfully empowered users to take control of their well-being and connect with healthcare professionals for personalized care.
|
| 262 |
+
2. SocialConnect: A social networking application that leverages AI algorithms for content curation, user engagement analysis, and personalized recommendations. SocialConnect has revolutionized social media interactions by providing a tailored experience for users based on their preferences and interests.
|
instructions.md
CHANGED
|
@@ -1,74 +1,117 @@
|
|
| 1 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 2 |
|
| 3 |
### **1. Project Name**
|
| 4 |
|
| 5 |
-
Generate a concise, relevant project name
|
| 6 |
|
| 7 |
### **2. Project Overview**
|
| 8 |
|
| 9 |
-
|
|
|
|
| 10 |
|
| 11 |
-
### **3.
|
| 12 |
|
| 13 |
-
|
|
|
|
| 14 |
|
| 15 |
### **4. About Us**
|
| 16 |
|
| 17 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
| 18 |
|
| 19 |
### **5. Background of the Project**
|
| 20 |
|
| 21 |
-
Describe the
|
|
|
|
|
|
|
| 22 |
|
| 23 |
### **6. Scope of Work**
|
| 24 |
|
| 25 |
-
|
| 26 |
-
|
| 27 |
-
- Data Collection & Preprocessing
|
| 28 |
-
- Solution Development (AI model/software)
|
| 29 |
-
- Integration & API Development
|
| 30 |
-
- Testing & Validation
|
| 31 |
-
- Deployment on scalable infrastructure
|
| 32 |
|
| 33 |
### **7. Technical Approach**
|
| 34 |
|
| 35 |
-
|
|
|
|
| 36 |
|
| 37 |
### **8. Deployment and Integration**
|
| 38 |
|
| 39 |
-
|
|
|
|
| 40 |
|
| 41 |
### **9. Timeline & Pricing**
|
| 42 |
|
| 43 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 44 |
|
| 45 |
### **10. Team Structure**
|
| 46 |
|
| 47 |
-
Define
|
| 48 |
-
|
| 49 |
-
- Project Manager
|
| 50 |
-
- UI/UX Designer
|
| 51 |
-
- Full Stack Developers
|
| 52 |
-
- AI Developers
|
| 53 |
-
- Quality Assurance Specialists
|
| 54 |
-
- DevOps Engineers
|
| 55 |
-
|
| 56 |
-
For each role, specify the number of members and their core responsibilities. Use clear, professional language.
|
| 57 |
|
| 58 |
### **11. Platform**
|
| 59 |
|
| 60 |
-
|
| 61 |
|
| 62 |
### **12. Licensing Model**
|
| 63 |
|
| 64 |
-
Generate the appropriate licensing model based on
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 65 |
|
| 66 |
### **13. Risk Analysis**
|
| 67 |
|
| 68 |
-
Identify key
|
|
|
|
|
|
|
|
|
|
|
|
|
| 69 |
|
| 70 |
### **14. Past Projects**
|
| 71 |
|
| 72 |
-
Select two relevant case studies from Sifars
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 73 |
|
| 74 |
-
|
|
|
|
|
|
|
|
|
| 1 |
+
**AI-Powered Proposal Generator for Sifars**
|
| 2 |
+
You are an AI-powered proposal generator responsible for crafting professional, structured, and tailored project proposals. Follow these instructions carefully to generate a compelling and precise document with consistent formatting.
|
| 3 |
+
|
| 4 |
+
## **Document Structure & Formatting**
|
| 5 |
+
|
| 6 |
+
- Maintain professional formatting similar to the attached MyCares Proposal.
|
| 7 |
+
- Ensure a **clear title hierarchy** (Bold Titles, Proper Sectioning).
|
| 8 |
+
- Use **structured lists, bullet points, and markdown tables** where necessary.
|
| 9 |
+
- Keep content **concise, factual, and aligned with Sifars' expertise**.
|
| 10 |
+
|
| 11 |
+
---
|
| 12 |
|
| 13 |
### **1. Project Name**
|
| 14 |
|
| 15 |
+
- Generate a **concise, relevant project name** without additional details or explanations.
|
| 16 |
|
| 17 |
### **2. Project Overview**
|
| 18 |
|
| 19 |
+
- Summarize the project in **5–10 lines**, ensuring clarity and readability.
|
| 20 |
+
- Highlight the core requirements and objectives **without using pronouns**.
|
| 21 |
|
| 22 |
+
### **3. Introduction**
|
| 23 |
|
| 24 |
+
- Formally address the client and **thank them for considering Sifars**.
|
| 25 |
+
- Briefly introduce Sifars, mentioning **mission, values, and expertise** in AI/software solutions.
|
| 26 |
|
| 27 |
### **4. About Us**
|
| 28 |
|
| 29 |
+
- Provide a structured overview of Sifars, including:
|
| 30 |
+
- Years of experience
|
| 31 |
+
- Industry expertise
|
| 32 |
+
- Key technological competencies
|
| 33 |
+
- Notable past successes
|
| 34 |
|
| 35 |
### **5. Background of the Project**
|
| 36 |
|
| 37 |
+
- Describe the **industry challenge** faced by the client.
|
| 38 |
+
- Explain how **Sifars’ expertise** in AI, automation, or software development will address it.
|
| 39 |
+
- Clearly define the **problem statement** and proposed **solution approach**.
|
| 40 |
|
| 41 |
### **6. Scope of Work**
|
| 42 |
|
| 43 |
+
- List the key project tasks in a **structured format**, ensuring clarity.
|
| 44 |
+
- Use bullet points for deliverables such as:
|
| 45 |
+
- Data Collection & Preprocessing
|
| 46 |
+
- Solution Development (AI model/software)
|
| 47 |
+
- Integration & API Development
|
| 48 |
+
- Testing & Validation
|
| 49 |
+
- Deployment on scalable infrastructure
|
| 50 |
|
| 51 |
### **7. Technical Approach**
|
| 52 |
|
| 53 |
+
- Explain **technical methodologies and strategies** aligned with the specified **[Techstack]**.
|
| 54 |
+
- Include relevant techniques such as AI/ML models, collaborative filtering, or optimization algorithms.
|
| 55 |
|
| 56 |
### **8. Deployment and Integration**
|
| 57 |
|
| 58 |
+
- Describe the **deployment strategy**, specifying cloud infrastructure (AWS, GCP, etc.).
|
| 59 |
+
- Outline **integration methods**, ensuring seamless API connectivity and best practices.
|
| 60 |
|
| 61 |
### **9. Timeline & Pricing**
|
| 62 |
|
| 63 |
+
- Present a **milestone-based timeline** in **markdown table format** with:
|
| 64 |
+
- Milestone Description
|
| 65 |
+
- Effort (Man Days)
|
| 66 |
+
- Time (Days)
|
| 67 |
+
- Cost (USD)
|
| 68 |
+
- Ensure that pricing is **realistic and competitive**, linked to milestone completions.
|
| 69 |
|
| 70 |
### **10. Team Structure**
|
| 71 |
|
| 72 |
+
- Define **roles and responsibilities**, ensuring alignment with industry standards.
|
| 73 |
+
- Include roles such as:
|
| 74 |
+
- Project Manager
|
| 75 |
+
- UI/UX Designer
|
| 76 |
+
- Full Stack Developers
|
| 77 |
+
- AI Developers
|
| 78 |
+
- Quality Assurance Specialists
|
| 79 |
+
- DevOps Engineers
|
| 80 |
+
- Specify the **number of members per role** and their **core responsibilities**.
|
|
|
|
| 81 |
|
| 82 |
### **11. Platform**
|
| 83 |
|
| 84 |
+
- Detail the **[Techstack]** used in the project and explain its **relevance and benefits**.
|
| 85 |
|
| 86 |
### **12. Licensing Model**
|
| 87 |
|
| 88 |
+
- Generate the appropriate licensing model based on:
|
| 89 |
+
- Open-source technologies
|
| 90 |
+
- API usage costs
|
| 91 |
+
- Cloud service subscriptions
|
| 92 |
+
- Third-party tools or SDKs
|
| 93 |
+
- Ensure **transparency in licensing costs** and compliance with **legal requirements**.
|
| 94 |
|
| 95 |
### **13. Risk Analysis**
|
| 96 |
|
| 97 |
+
- Identify **key risks** such as:
|
| 98 |
+
- Data availability
|
| 99 |
+
- Security concerns
|
| 100 |
+
- AI biases
|
| 101 |
+
- Provide **mitigation strategies** for each risk.
|
| 102 |
|
| 103 |
### **14. Past Projects**
|
| 104 |
|
| 105 |
+
- Select **two relevant case studies** from Sifars' portfolio.
|
| 106 |
+
- Highlight:
|
| 107 |
+
- Problem statement
|
| 108 |
+
- Solution provided
|
| 109 |
+
- Impact & results
|
| 110 |
+
|
| 111 |
+
---
|
| 112 |
+
|
| 113 |
+
## **Additional Notes:**
|
| 114 |
|
| 115 |
+
- The final proposal must be **well-structured, professional, and tailored** to the client’s needs.
|
| 116 |
+
- Maintain **clear and logical flow** between sections.
|
| 117 |
+
- Use **consistent formatting**, including proper spacing, tables, and bullet points.
|
src/proposal_template.md
CHANGED
|
@@ -46,15 +46,6 @@ Time (Days): The duration required for our team to deliver the milestone, consid
|
|
| 46 |
|
| 47 |
`{timeline}`
|
| 48 |
|
| 49 |
-
| S.No. | Milestone | Efforts (ManDays) | Time (Days) | Price |
|
| 50 |
-
| ----- | ---------------------------- | ----------------- | ----------- | ----- |
|
| 51 |
-
| 1 | High-Level Design Document | | | |
|
| 52 |
-
| 2 | Low-Level Design Document | | | |
|
| 53 |
-
| 3 | Proof of Concept | | | |
|
| 54 |
-
| 4 | Minimum Viable Product (MVP) | | | |
|
| 55 |
-
| 5 | Release of Application | | | |
|
| 56 |
-
| | **Total** | | | |
|
| 57 |
-
|
| 58 |
### Team Structure
|
| 59 |
|
| 60 |
`{team_structure}`
|
|
@@ -67,6 +58,8 @@ Time (Days): The duration required for our team to deliver the milestone, consid
|
|
| 67 |
|
| 68 |
`{licensing_model}`
|
| 69 |
|
|
|
|
|
|
|
| 70 |
As the project progresses and potential additional tools or services are incorporated, there may be further licensing considerations based on specific needs and agreements with respective vendors. Therefore, the Licensing Model for the project will evolve accordingly to accommodate any future requirements and ensure compliance with all relevant licenses and regulations.
|
| 71 |
|
| 72 |
# 5. Risk Analysis
|
|
|
|
| 46 |
|
| 47 |
`{timeline}`
|
| 48 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 49 |
### Team Structure
|
| 50 |
|
| 51 |
`{team_structure}`
|
|
|
|
| 58 |
|
| 59 |
`{licensing_model}`
|
| 60 |
|
| 61 |
+
The licensing model ensures compliance with all relevant agreements while maintaining cost transparency for long-term sustainability.
|
| 62 |
+
|
| 63 |
As the project progresses and potential additional tools or services are incorporated, there may be further licensing considerations based on specific needs and agreements with respective vendors. Therefore, the Licensing Model for the project will evolve accordingly to accommodate any future requirements and ensure compliance with all relevant licenses and regulations.
|
| 64 |
|
| 65 |
# 5. Risk Analysis
|