[Feature]: An innovative approach to develop microservices by spec-driven development
- Langage dominant
- Python
- Étoiles
- 137k
- Forks
- 12.3k
- Merge moyen
- 2 j 12 h
- PR mergées (30 j)
- 159
Description
### Problem Statement
Dear Copilot Team,
I hope this message finds you well.
I would like to briefly introduce an AI-assisted, documentation-driven software development methodology that I have designed and validated through a real-world microservice application.
The method enables structured, scalable development of large systems by combining human-defined use cases with AI-driven implementation. It addresses common limitations of large-scale AI-assisted coding—such as architectural drift, duplication, and context fragmentation—through controlled documentation and incremental expansion.
Using this approach, I built a sample event-driven microservice application with full back-end and front-end validation and bilingual support.
You can find an explanation of the methodology, along with access to the sample application and repositories in attached introduction PDF here.
[Approach Introduction.pdf](https://github.com/user-attachments/files/28539201/Approach.Introduction.pdf)
If the approach aligns with your current or future development initiatives, I would be glad to explore potential collaboration opportunities.
Best regards,
Mojtaba Kargaran
### Proposed Solution
Described in attached pdf above.
### Alternatives Considered
_No response_
### Component
Specify CLI (initialization, commands)
### AI Agent (if applicable)
None
### Use Cases
_No response_
### Acceptance Criteria
_No response_
### Additional Context
_No response_
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Start by reading the attached Approach Introduction.pdf and then inspect the repository's CLI initialization and command entry points. The issue provides no concrete use case, files, or acceptance criteria, so define a scoped change and measurable completion criteria before implementation can begin.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- ai, cli, developer-experience
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- Active
- Clarté
- À clarifier
- Accessibilité débutants
- 18/100