openspec-stack-init 1.0.2 → 1.0.3

package/README.md

@@ -19,14 +19,30 @@ npx openspec-stack-init ./my-project --dry-run
 
 ## What it installs
 
-| Tool | What it does | Non-interactive flag used |
+| Tool | What it does | How |
 |---|---|---|
-| **OpenSpec** | Spec-driven development | `openspec init --tools claude --profile expanded --force` |
-| **Beads** | Git-backed issue tracker / agent memory | `bd init --quiet` + `bd setup claude` |
+| **OpenSpec** | Spec-driven development | `openspec init --tools claude --profile core --force` |
+| **Beads** | Git-backed issue tracker / agent memory | `bd init --quiet` + `bd setup claude` (CLI hooks) |
 | **claude-mem** | Automatic session memory via hooks | `claude plugin marketplace add` + `claude plugin install` |
 | **openspec-to-beads** | Syncs OpenSpec tasks.md → Beads issues | `npx @smithery/cli skill add` |
 | **/migrate-to-openspec** | Brownfield migration skill | Copied to `.claude/skills/migrate-to-openspec/` |
 
+### Beads: CLI vs Claude Code Plugin
+
+This package installs **Beads CLI level** only:
+
+- `bd init` — creates `.beads/` and `issues.jsonl` in your project (git-committed)
+- `bd setup claude` — installs `SessionStart` and `PreCompact` hooks so Claude Code gets task context automatically
+
+There is also an **optional Beads Claude Code Plugin** that adds slash commands (`/beads:ready`, `/beads:create`, etc.) and an MCP server. It cannot be installed automatically from a shell script — install it manually inside Claude Code if you want it:
+
+```
+/plugin marketplace add steveyegge/beads
+/plugin install beads
+```
+
+For most projects the CLI level is sufficient — Claude Code agents call `bd` via bash.
+
 ## Prerequisites
 
 > ⚠️ **This package does NOT install the tools below for you.**
@@ -101,4 +117,4 @@ node src/index.js ./target-project
 ```bash
 npm publish --access public
 # Then anyone can run: npx openspec-stack-init
-```
+```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "openspec-stack-init",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "type": "module",
   "description": "Initialize OpenSpec + Beads + claude-mem + skills in any project",
   "author": {

package/src/index.js

@@ -226,6 +226,13 @@ if (existsSync(join(TARGET_DIR, "openspec"))) {
   const ok = run("openspec init --tools claude --profile core --force");
   if (ok) {
     log.ok("OpenSpec initialized (core profile, Claude tools)");
+
+    // Remove default config.yaml so custom template can be written in Step 3
+    const defaultConfig = join(TARGET_DIR, "openspec", "config.yaml");
+    if (existsSync(defaultConfig)) {
+      unlinkSync(defaultConfig);
+    }
+
     // Switch to expanded profile to unlock: new, ff, verify, sync, bulk-archive, onboard
     // openspec config profile sets the global default, openspec update regenerates skill files
     const expanded = run("openspec config profile expanded", { silent: true }) &&
@@ -258,7 +265,7 @@ context: |
 
   # TODO: fill in your actual stack and conventions
   # Tech stack: e.g. TypeScript, React, Node.js / Unity, C# / Python, Django
-  # Architecture: e.g. MVC, HMVC, ECS, microservices
+  # Architecture: e.g. MVC, HMVC, ECS, Redux, MVVM, microservices
   # Testing: e.g. Jest, NUnit, pytest
   # Key constraints: e.g. legacy codebase, must support IE11, no breaking API changes
 
@@ -266,6 +273,7 @@ rules:
   proposal:
     - Always include a rollback plan for legacy code changes
     - List all affected modules
+    - Always include an "## Alternatives Considered" section listing at least 2 alternative approaches with their pros, cons, and reason for rejection. Format each as: "### Option: <name> / Pros: ... / Cons: ... / Why rejected: ..."
   specs:
     - Use Given/When/Then format for scenarios
   design: