feat(aidd-craft): start a project from scratch with craft practices
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 5/5
- 預估耗時
- 一週以上
- 新手友好度
- 35/100
- Issue 類型
- 功能
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
研究方向
Start with the linked child issues #1260–#1265 and read the existing aidd-context rule generator, project memory, and onboarding flow; those are the named integration points. Then review how aidd-orchestrator dispatches isolated runs and how aidd-telemetry measures tokens. Done means the opt-in and init/tdd flow meet the listed success evidence, including test-first behavior, chosen rules, architecture, and recorded run duration.
由索引模型根據 Issue 內容生成。
描述
Outcome
A developer starting an empty project can opt into craft practices and ship the first use case test-driven, the architecture emerging from it.
Context and value
Developers who practice craftsmanship, or want to learn it, get the practices without writing their own prompts. Projects that do not want them never see them: the plugin is opt-in.
Boundaries
- Includes: the onboarding opt-in;
init(default rules, optional practices, expected architecture in project memory);tdd(analyze, then cycle; interactive and autonomous). - Excludes: audit, BDD and Example Mapping, Event Storming, iteration typing, scaffolding, new agents, any change to
aidd-dev.
Principles
- Rules carry the practice content; skills stay light and deterministic.
aidd-contextwrites the rules and the project memory;aidd-craftsupplies their content.- No scaffolding: memory describes the expected architecture (one Bounded Context to start, one Clean Architecture per context), the first use case built test-driven creates it.
- Coexists with
aidd-context:01-bootstrap: bootstrap decides the deployable units and stops atsrc/, craft describes what lives inside. - Tool- and cloud-agnostic. Practice terms are worded neutrally.
Success evidence
On an empty project, the onboarding asks, options are chosen, and the first use case goes through tdd:
- every behavior had a failing test before its code;
- the resulting tree matches the architecture described in memory;
- only the chosen rules are installed;
- tokens per iteration are measured with
aidd telemetry, one declared task per iteration, and the run's duration is recorded alongside, since telemetry counts tokens, not time.
Dependencies and unknowns
| Item | Kind | Handling |
|---|---|---|
aidd-context rule generator and project memory |
dependency | craft supplies content, never writes rules itself |
aidd-orchestrator dispatching two isolated runs |
dependency | story: autonomous TDD |
| Mutation testing | decision | separate task |
aidd-telemetry, beta and opt-in |
dependency | needed only to measure the success evidence |
Children
- #1260
- #1261
- #1262
- #1263
- #1264
- #1265
- 主要語言
- TypeScript
- 星號
- 481
- 分支
- 45
- 平均合併
- 1 天 13 小時
- 30 天內合併 PR
- 91
環境準備
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
ai-driven-dev/framework 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 86/100
ai-driven-dev/framework#1311 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 79/100
ai-driven-dev/framework#1244 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
ai-driven-dev/framework#1197 ·
維護者通常 1 天內回覆
-
refactor(aidd-context): apply the new skill template to learn可能已有人在做 @blafourcade 於 3 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
ai-driven-dev/framework#1186 · 已指派 1 人 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 83/100
ai-driven-dev/framework#1163 · 1 則留言 ·
維護者通常 1 天內回覆
查看 ai-driven-dev/framework 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 82/100
solidjs/solid-docs#1716 ·
維護者通常 1 天內回覆
-
bug needs-triage
難度 2/5 1-3 小時 新手友好度 72/100
維護者通常 1 天內回覆
-
Progress indicated by console logs is off by one可能已有人在做 @marceliwac 今天認領。 未關閉bug needs-triage
難度 2/5 1-3 小時 新手友好度 76/100
aws-samples/aws-cdk-examples#1336 ·
-
難度 2/5 1-3 小時 新手友好度 74/100
melgarafael/DeskcommCRM#4999 · 1 則留言 ·
維護者通常 1 天內回覆
-
type: bug
難度 2/5 1-3 小時 新手友好度 78/100
nrwl/nx#37955 · 1 個 reaction ·
維護者通常 2 天內回覆