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

Aperta
#1,259 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
typescript

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
TypeScript
Stelle
481
Fork
45
Merge medio
1g 13h
PR unite (30g)
91

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ai-driven-dev/framework

Tutte le issue di ai-driven-dev/framework

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.