@rasensio/aidlc-content 1.7.0 → 1.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@rasensio/aidlc-content",
3
- "version": "1.7.0",
3
+ "version": "1.8.0",
4
4
  "type": "module",
5
5
  "main": "dist/index.js",
6
6
  "types": "dist/index.d.ts",
@@ -17,7 +17,8 @@
17
17
  "templates/",
18
18
  "guidance/",
19
19
  "capabilities/",
20
- "phases/"
20
+ "phases/",
21
+ "tutorials/"
21
22
  ],
22
23
  "engines": {
23
24
  "node": ">=18.0.0"
@@ -0,0 +1,64 @@
1
+ ---
2
+ title: "Getting Started with AIDLC"
3
+ description: "Learn how to set up AIDLC in your project and run your first lifecycle session."
4
+ order: 1
5
+ slug: getting-started
6
+ ---
7
+
8
+ ## Step 1: Install and Set Up AIDLC
9
+
10
+ AIDLC works with Claude Code, Cursor, Windsurf, Kiro, and Codex. One command sets everything up — run it interactively to choose platforms, scope, and a default template, or pass `--platform` to skip the prompts:
11
+
12
+ ```bash
13
+ # Interactive setup — choose platforms, scope, and default template
14
+ npx @rasensio/aidlc init
15
+
16
+ # Or set up directly for a single platform, no prompts
17
+ npx @rasensio/aidlc init --platform claude-code
18
+ ```
19
+
20
+ Either way, `init` creates a `.aidlc/` directory with the canonical lifecycle skills, plus platform-native activation files (for example `.claude/skills/` for Claude Code or `.cursor/rules/` for Cursor). It also scans your codebase and generates context documents under `.aidlc/context/` so your AI assistant starts with real knowledge of the project.
21
+
22
+ ## Step 2: Choose a Workflow Template
23
+
24
+ Templates define which lifecycle phases apply to a piece of work, so a one-line fix doesn't go through the same ceremony as a new feature. AIDLC ships with five:
25
+
26
+ - **full-feature** — the full lifecycle from ideation through maintenance, with adversarial review gates on requirements and design.
27
+ - **quick-feature** — standard scope, from requirements through deployment.
28
+ - **bugfix** — like quick-feature but with reproduction steps and no design phase.
29
+ - **spike** — research and exploration, ending in a findings document.
30
+ - **micro-task** — implementation and testing only, for small changes.
31
+
32
+ For your first session, try the {{ref:template/full-feature}} template — it exercises every phase, so you see the whole process once.
33
+
34
+ ## Step 3: Start a Session
35
+
36
+ Start a lifecycle instance from the template. The instance gets its own state directory under `.aidlc/state/`, tracking which phase is active and which artifacts are complete:
37
+
38
+ ```bash
39
+ aidlc start full-feature --name my-feature
40
+ ```
41
+
42
+ The first phase for a full-scope instance is ideation. When you open your AI assistant in this project, the {{ref:skill/aidlc-ideation}} skill activates and guides it to explore the problem space and produce an `idea.md` artifact before any code is written.
43
+
44
+ ## Step 4: Check Progress and Continue
45
+
46
+ Each phase produces required artifacts, and phase transitions are gated on their completion. Three commands drive the day-to-day loop:
47
+
48
+ ```bash
49
+ aidlc status # progress across all active instances
50
+ aidlc continue # resume the active instance at its next step
51
+ aidlc transition my-feature # evaluate gates and advance to the next phase
52
+ ```
53
+
54
+ If a transition is blocked, the output lists exactly what's missing — incomplete artifacts, unresolved review findings, or phases that must finish first. Your AI assistant reads the same state, so `aidlc continue` in a fresh session picks up precisely where the last one left off.
55
+
56
+ ## Step 5: Enforce Gates in CI
57
+
58
+ Gates aren't just advisory — `aidlc gate <instance> <phase>` exits with code 0 when a phase is complete and 1 when it isn't, so your pipeline can block merges until the lifecycle catches up. This sample GitHub Actions workflow is inlined from the repository at build time, so it always matches the current release:
59
+
60
+ ```yaml source=ci/aidlc-gate.yml
61
+ # Contents inlined from ci/aidlc-gate.yml at build time
62
+ ```
63
+
64
+ That's the whole loop: set up once, pick a template per piece of work, and let the gates keep quality honest. Browse the rest of the docs to see what each phase skill does in detail.