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

オープン
#1,259 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
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時間
マージ済み PR(30日)
91

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

ai-driven-dev/framework のほかの issue

ai-driven-dev/framework の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。