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

Offen
#1,259 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
typescript

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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
Vorherrschende Sprache
TypeScript
Sterne
481
Forks
45
Ø Merge
1 T. 13 Std.
Gemergte PRs (30 T.)
91

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus ai-driven-dev/framework

Alle Issues in ai-driven-dev/framework

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.