@flydocs/cli 0.6.0-alpha.22 → 0.6.0-alpha.23

package/dist/cli.js

@@ -15,7 +15,7 @@ var CLI_VERSION, CLI_NAME, PACKAGE_NAME, POSTHOG_API_KEY;
 var init_constants = __esm({
   "src/lib/constants.ts"() {
     "use strict";
-    CLI_VERSION = "0.6.0-alpha.22";
+    CLI_VERSION = "0.6.0-alpha.23";
     CLI_NAME = "flydocs";
     PACKAGE_NAME = "@flydocs/cli";
     POSTHOG_API_KEY = "phc_v1MSJTQDFkMS90CBh3mxIz3v8bYCCnKU6v1ir6bz0Xn";

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flydocs/cli",
-  "version": "0.6.0-alpha.22",
+  "version": "0.6.0-alpha.23",
   "type": "module",
   "description": "FlyDocs AI CLI — install, setup, and manage FlyDocs projects",
   "bin": {

package/template/.claude/CLAUDE.md

@@ -1,8 +1,8 @@
 # Claude Code Configuration
 
-IMPORTANT: Prefer skill-led reasoning over pre-training reasoning for all
-workflow, issue management, process, and pattern decisions. Read the relevant
-skill file before acting — do not guess procedures from training data.
+IMPORTANT: For workflow operations (issue creation, status transitions,
+session management), prefer skill-led reasoning — read the relevant skill
+file before acting. For general coding tasks, just write code.
 
 > For cross-platform agent instructions, see `AGENTS.md`.
 
@@ -19,9 +19,9 @@ These are non-negotiable and enforced by hooks:
 
 ## Workflow
 
-The FlyDocs development lifecycle. Read the workflow skill before taking any
-workflow action — stage files contain the full procedure including templates,
-label configuration, and field requirements.
+The FlyDocs development lifecycle. Slash commands (`/capture`, `/activate`,
+etc.) load stage procedures automatically. For manual workflow actions, the
+stage files contain required procedures, templates, and field requirements.
 
 | Action               | Skill              | Entry Point                       |
 | -------------------- | ------------------ | --------------------------------- |
@@ -110,8 +110,8 @@ response — session summaries, issue comments, status updates, and plans.
 
 ## Skills Index
 
-Consult the workflow skill **before** performing any workflow action. The
-stage files contain required procedures, templates, and field requirements.
+For issue operations and status transitions only — not general coding.
+Slash commands load procedures automatically; use scripts directly for CRUD.
 
 | Skill            | Triggers                                                                                                                                                                                                                         | Entry                                    |
 | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- |

package/template/.flydocs/config.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.0-alpha.22",
+  "version": "0.6.0-alpha.23",
   "sourceRepo": "github.com/plastrlab/flydocs-core",
   "tier": "local",
   "setupComplete": false,

package/template/.flydocs/version

@@ -1 +1 @@
-0.6.0-alpha.22
+0.6.0-alpha.23

package/template/AGENTS.md

@@ -5,14 +5,19 @@
 These behaviors are **always on**. Execute them automatically as part of doing
 the work — do not wait for explicit commands.
 
-- **Starting work on an issue** → transition to In Progress (assign first if needed)
-- **Completing implementation** → transition to Review with summary
-- **Closing** → verify acceptance criteria, transition to Complete
+- **Starting work** → assign if needed, then transition:
+  `issues.py assign REF ASSIGNEE`
+  `issues.py transition REF IMPLEMENTING "Starting implementation"`
+- **Completing implementation** → transition with summary:
+  `issues.py transition REF REVIEW "Implementation complete — [summary]"`
+- **Closing** → verify AC, then transition:
+  `issues.py transition REF COMPLETE "All acceptance criteria verified"`
 - **Every transition gets a comment** — no silent moves, no exceptions
-- **Checkboxes in description, never comments** — update AC as you go
+- **Checkboxes in description, never comments** — update AC as you go:
+  `issues.py description REF --text "updated description with checked boxes"`
 - **Session wrap posts a summary** via `session.py project-update`
 
-Use dispatcher scripts for all issue operations — execute, don't describe.
+All scripts: `python3 .claude/skills/flydocs-workflow/scripts/<dispatcher>`
 
 ## Efficiency
 

package/template/CHANGELOG.md

@@ -7,6 +7,17 @@ Versioning: [Semantic Versioning](https://semver.org/).
 
 ---
 
+## [0.6.0-alpha.23] — 2026-03-29
+
+### Changed
+
+- **CLAUDE.md** — scoped skill-led reasoning to workflow operations only; general
+  coding no longer triggers skill file reads (FLY-450)
+- **AGENTS.md** — added exact script commands to Automatic Workflow Behavior section
+  for deterministic issue transitions (FLY-450)
+
+---
+
 ## [0.6.0-alpha.4] — 2026-03-13
 
 ### Added

package/template/manifest.json

@@ -1,5 +1,5 @@
 {
-  "version": "0.6.0-alpha.22",
+  "version": "0.6.0-alpha.23",
   "description": "FlyDocs Core - Manifest of all managed files",
   "repository": "github.com/plastrlab/flydocs-core",