feat(aidd-craft): start a project from scratch with craft practices

未關閉
#1,259 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 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-context writes the rules and the project memory; aidd-craft supplies 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 at src/, 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

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ai-driven-dev/framework 的其他 Issue

查看 ai-driven-dev/framework 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。