github / github/spec-kit

[Feature]: An innovative approach to develop microservices by spec-driven development

Open
#2,829 1 comment 0 reactions 0 assignees View on GitHub
enhancement stale
Dominant language
Python
Stars
137k
Forks
12.3k
Avg merge
2d 12h
Merged PRs (30d)
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_

Contributor guide

Open the contributing guide

Research direction

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.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
ai, cli, developer-experience
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
18/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.