@rasensio/aidlc 0.1.0 → 0.2.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rasensio/aidlc",
-  "version": "0.1.0",
+  "version": "0.2.0",
   "description": "AI Development Lifecycle Framework — structured lifecycle guidance for AI coding agents across platforms",
   "type": "module",
   "main": "dist/cli.js",
@@ -15,7 +15,10 @@
     "test": "vitest run",
     "test:watch": "vitest",
     "lint": "tsc --noEmit",
-    "prepublishOnly": "npm run build && npm test"
+    "prepublishOnly": "npm run build && npm test",
+    "release:patch": "npm version patch && npm publish --access public && git push --follow-tags",
+    "release:minor": "npm version minor && npm publish --access public && git push --follow-tags",
+    "release:major": "npm version major && npm publish --access public && git push --follow-tags"
   },
   "keywords": [
     "ai",

package/skills/01-getting-started.md

@@ -0,0 +1,127 @@
+---
+name: aidlc-getting-started
+description: Helps users get started with AIDLC — responds to onboarding questions, suggests templates, and guides first steps
+phase: ideation
+priority: 95
+trigger: When the user asks how to get started, how to use the framework, or asks about fixing bugs, adding features, or beginning work
+---
+# Getting Started with AIDLC
+
+## When to Activate
+
+Respond using this skill when the user asks any of the following:
+- "How do I get started?"
+- "How do I fix a bug?"
+- "How do I add a feature?"
+- "What should I do first?"
+- "How does this lifecycle thing work?"
+- "What template should I use?"
+- "Help me start working on X"
+
+## Quick Answers
+
+### "How do I fix a bug?"
+
+1. Start a bugfix lifecycle instance:
+   ```
+   aidlc start bugfix --name <short-description>
+   ```
+2. This creates a focused workflow: reproduce the bug → fix it → test it → deploy.
+3. Run `aidlc continue <name>` to see what step to do next.
+4. The bugfix template skips the design phase and requires a `reproduction.md` artifact first.
+
+### "How do I add a feature?"
+
+For a small, well-defined feature:
+```
+aidlc start quick-feature --name <feature-name>
+```
+
+For a larger feature needing design and review:
+```
+aidlc start full-feature --name <feature-name>
+```
+
+For something tiny (just code + test):
+```
+aidlc start micro-task --name <task-name>
+```
+
+### "How do I explore an idea or do research?"
+
+```
+aidlc start spike --name <research-topic>
+```
+This gives you Ideation + Requirements phases only — no implementation pressure.
+
+### "What should I do next?"
+
+Run:
+```
+aidlc continue
+```
+This tells you exactly which artifact to produce or which phase to enter next.
+
+### "How do I check progress?"
+
+```
+aidlc status
+```
+Shows all active lifecycle instances with completion %, current phase, and stall detection.
+
+### "How does the lifecycle work?"
+
+AIDLC guides your work through phases:
+
+1. **Ideation** — What are we building and why?
+2. **Requirements** — What are the acceptance criteria?
+3. **Design** — How will we build it?
+4. **Implementation** — Write the code
+5. **Testing** — Verify it works
+6. **Deployment** — Ship it
+7. **Maintenance** — Keep it running
+
+Not every task needs all phases. The templates handle this:
+- **micro-task** → Implementation + Testing only
+- **quick-feature** → Requirements through Deployment
+- **full-feature** → All 7 phases with review gates
+- **bugfix** → Requirements (reproduction) + Implementation + Testing + Deployment
+- **spike** → Ideation + Requirements (research) only
+
+### "How do I set up AIDLC in this project?"
+
+If AIDLC is already installed (you can see `.aidlc/skills/` in the project), just start using it:
+```
+aidlc start <template>
+```
+
+If not installed yet:
+```
+aidlc setup
+```
+This runs an interactive wizard that configures the framework for your project.
+
+## Choosing the Right Template
+
+| You want to... | Use this template | Scope |
+|---------------|-------------------|-------|
+| Fix a bug | `bugfix` | Standard (no design) |
+| Add a small feature | `quick-feature` | Standard |
+| Build something complex | `full-feature` | Full (with review gates) |
+| Just write code + test | `micro-task` | Micro |
+| Research / explore | `spike` | Ideation + Requirements |
+
+## After Starting
+
+Once you've started an instance, the framework tracks your progress. At any point:
+- `aidlc continue` — what to do next
+- `aidlc status` — overall progress
+- `aidlc gate <instance> <phase>` — check if a phase is complete
+- `aidlc transition <instance>` — advance to the next phase
+
+## State Location
+
+All lifecycle state lives in `.aidlc/state/<instance-name>/`. It's just YAML files — you can read them directly if needed. The key files are:
+- `instance.yaml` — which template, scope, and current phase
+- `phase-<name>.yaml` — artifact completion for each phase
+- `transitions.log` — history of phase transitions