@fledge/workflow 0.4.0 → 0.5.0

package/dist/scripts/brief.js

@@ -1,6 +1,6 @@
 #!/usr/bin/env node
 import { i as runMain, n as writeFrontmatter, r as defineCommand, t as parseFrontmatter } from "./frontmatter-BUnjSmTA.js";
-import { cwd, stdout } from "node:process";
+import { cwd, env, stdout } from "node:process";
 import fs from "node:fs";
 import path from "node:path";
 Object.freeze({ status: "aborted" });
@@ -3679,12 +3679,21 @@ const tasksFrontmatter = object({ tasks: array(object({
 //#region ../cli/dist/brief.js
 const BRIEFS_DIRECTORY = path.join(".fledge", "briefs");
 /**
+* Returns the project root directory.
+* Uses the `FLEDGE_PROJECT_DIR` environment variable if set, otherwise falls back to `cwd()`.
+*
+* @returns The absolute path to the project root.
+*/
+function getProjectRoot() {
+	return env.FLEDGE_PROJECT_DIR || cwd();
+}
+/**
 * Returns the absolute path to the briefs directory for the current project.
 *
-* @returns The absolute path to `.fledge/briefs/` in the current working directory.
+* @returns The absolute path to `.fledge/briefs/` in the project root.
 */
 function getBriefsDirectory() {
-	return path.join(cwd(), BRIEFS_DIRECTORY);
+	return path.join(getProjectRoot(), BRIEFS_DIRECTORY);
 }
 /**
 * Returns the absolute path to a specific brief's directory.

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@fledge/workflow",
   "type": "module",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "author": "René Schapka",
   "license": "MIT",
   "files": [
@@ -15,7 +15,7 @@
     "node": ">=24"
   },
   "dependencies": {
-    "@fledge/cli": "^0.7.0"
+    "@fledge/cli": "^0.8.0"
   },
   "devDependencies": {
     "@antfu/eslint-config": "7.7.3",

package/skills/brief/SKILL.md

@@ -7,9 +7,19 @@ metadata:
   type: workflow
 ---
 
+## Setup
+
+Before running any script, set the `FLEDGE_PROJECT_DIR` environment variable to the project root so scripts know where to find and create briefs:
+
+```bash
+export FLEDGE_PROJECT_DIR="$(pwd)"
+```
+
+Set this once at the start of the conversation. All scripts below assume it is set.
+
 ## Available scripts
 
-Self-contained scripts bundled with this skill. Run from the skill directory with `node`:
+Self-contained executable scripts bundled with this skill:
 
 - **`scripts/brief.js create <name>`** -- Create a new brief with stub files
 - **`scripts/brief.js start <name>`** -- Transition a brief from draft to active
@@ -27,7 +37,7 @@ Ask what the user wants to do, or infer from context. Present these options:
 2. **Continue a brief** -- pick up an existing brief. Proceed to Step 4.
 3. **Complete a brief** -- wrap up a finished feature. Proceed to Step 5.
 
-If unclear, run `node scripts/brief.js list` to show current briefs and ask.
+If unclear, run `scripts/brief.js list` to show current briefs and ask.
 
 ---
 
@@ -35,7 +45,7 @@ If unclear, run `node scripts/brief.js list` to show current briefs and ask.
 
 Before writing anything, build an understanding of what exists.
 
-1. Run `node scripts/brief.js list --status completed` to read summaries of completed features. Note anything relevant to the new feature.
+1. Run `scripts/brief.js list --status completed` to read summaries of completed features. Note anything relevant to the new feature.
 2. Ask the user what they want to build. Keep it conversational, not a form. Aim to understand:
    - What is the user-facing change?
    - Why does it matter?
@@ -50,7 +60,7 @@ Proceed to Step 2.
 
 ## Step 2: Draft the brief
 
-Run `node scripts/brief.js create <name>` to create the brief directory.
+Run `scripts/brief.js create <name>` to create the brief directory.
 
 Write the brief content into `brief.md`. The frontmatter is managed by the scripts. The markdown body should capture:
 
@@ -86,7 +96,7 @@ tasks:
 
 Order tasks by dependency: tasks that others depend on come first within their group.
 
-After writing tasks, run `node scripts/brief.js validate <name>` to confirm the brief is valid, then run `node scripts/brief.js start <name>` to transition to active.
+After writing tasks, run `scripts/brief.js validate <name>` to confirm the brief is valid, then run `scripts/brief.js start <name>` to transition to active.
 
 Present the complete brief and task list to the user for review before starting.
 
@@ -94,22 +104,22 @@ Present the complete brief and task list to the user for review before starting.
 
 ## Step 4: Continue a brief
 
-Run `node scripts/brief.js list` to show all briefs. If the user does not specify which brief, ask them to pick one.
+Run `scripts/brief.js list` to show all briefs. If the user does not specify which brief, ask them to pick one.
 
-Run `node scripts/brief.js status <name>` to show progress. Read the brief and tasks files to understand the full context.
+Run `scripts/brief.js status <name>` to show progress. Read the brief and tasks files to understand the full context.
 
 From here, the user may want to:
 - **Discuss a task** -- talk through approach before implementing
 - **Update tasks** -- mark tasks as done, add new tasks, reorder
 - **Revise the brief** -- update scope or design decisions based on what was learned during implementation
 
-When updating task status, modify the `tasks.md` frontmatter directly, then run `node scripts/brief.js status <name>` to confirm the update.
+When updating task status, modify the `tasks.md` frontmatter directly, then run `scripts/brief.js status <name>` to confirm the update.
 
 ---
 
 ## Step 5: Complete a brief
 
-Run `node scripts/brief.js status <name>` to verify all tasks are done.
+Run `scripts/brief.js status <name>` to verify all tasks are done.
 
 If there are incomplete tasks, ask the user whether to:
 1. Mark remaining tasks as done (if they were completed outside this conversation)
@@ -120,4 +130,4 @@ Write a summary into the `brief.md` frontmatter `summary` field. The summary sho
 - What was built
 - Key decisions or patterns established that future features should know about
 
-Run `node scripts/brief.js complete <name>` to transition to completed. The script validates that all tasks are done and the summary is present.
+Run `scripts/brief.js complete <name>` to transition to completed. The script validates that all tasks are done and the summary is present.