document360-writer 0.4.53 → 0.4.55

package/dist/commands/devhints.d.ts

@@ -1,20 +1,25 @@
 import type { SlashCommandResult } from './index.js';
 import type { ReplContext } from '../repl.js';
 /** Bump when the guide content changes — lets a future check detect a stale committed guide. */
-export declare const DEV_HINTS_GUIDE_VERSION = 1;
+export declare const DEV_HINTS_GUIDE_VERSION = 2;
 /**
- * The committed protocol guide the SOURCE repo's coding agent follows to write doc hints. It is
- * self-contained because that agent has none of d360-writer's context (no tools, no system prompt) —
- * everything it needs to produce a valid hint is here. The /devhints command writes this to
- * `.d360-writer/DEV-HINTS-GUIDE.md`; the paste block (below) just points the source agent at it.
+ * The committed protocol guide the SOURCE repo's coding agent follows. Self-contained because that
+ * agent has none of d360-writer's context. Two parts: (1) a ONE-TIME architecture brief that onboards
+ * the docs agent — the builder, who holds the full intent, hands over what code alone can't tell a
+ * writer; (2) ONGOING per-change doc hints. The /devhints command writes this to
+ * `.d360-writer/DEV-HINTS-GUIDE.md`; the paste block points the source agent at it.
  */
 export declare function devHintsGuide(): string;
-/** `/devhints` — scaffold the hint channel: write the committed guide + emit a paste-ready block the
-    user adds to their SOURCE repo's CLAUDE.md/AGENTS.md so its coding agent starts leaving hints. */
+/** The human-owned creator-notes template (scaffolded once, never overwritten). The builder reads it
+    first as authoritative; the docs agent reads it as authoritative intent. */
+export declare function creatorNotesTemplate(): string;
+/** `/devhints` — scaffold the dev→docs hand-off: write the committed guide + the architecture inbox
+    (with a human creator-notes template) + the hints inbox, then emit a paste-ready block for the
+    SOURCE repo's CLAUDE.md/AGENTS.md so its coding agent onboards the docs agent and keeps it current. */
 export declare function devhintsCommand(_args: string[], ctx: ReplContext): Promise<SlashCommandResult>;
 /**
  * The paste-ready block for the user to add to their SOURCE repo's agent memory (CLAUDE.md/AGENTS.md).
- * A ONE-LINE pointer to the committed guide — not the protocol inline — so their memory stays lean and
- * we can improve the guide without anyone re-pasting. Mirrors renderTestidHandoff's bracketed shape.
+ * A pointer to the committed guide plus the ordered marching orders — not the protocol inline — so their
+ * memory stays lean and we can improve the guide without re-pasting. Mirrors renderTestidHandoff's shape.
  */
 export declare function renderDevHintsHandoff(): string[];

package/dist/commands/draft.d.ts

@@ -0,0 +1,27 @@
+import type { ReplContext } from '../repl.js';
+import type { SlashCommandResult } from './index.js';
+/** A feature available to draft: a subfolder of `.d360-writer/input/` holding ≥1 input doc. */
+export type DraftFeature = {
+    name: string;
+    docCount: number;
+};
+/** List the feature subfolders under `.d360-writer/input/` (each with ≥1 PRD/spec doc). Sorted.
+    Loose docs directly in input/ (no subfolder) surface as the synthetic feature "" (root). */
+export declare function listInputFeatures(cwd: string): {
+    features: DraftFeature[];
+    looseDocs: number;
+};
+/** Resolve a `/draft <selector>` to a feature subfolder: exact → prefix → fuzzy (substring), case-
+    insensitive. Returns the matched feature name, or null when nothing matches (caller treats the
+    selector as a free-text hint instead). */
+export declare function matchFeature(features: DraftFeature[], selector: string): string | null;
+/** The prompt that drives the draft-from-prd skill for a resolved scope. `feature` is the subfolder
+    (or '' for loose root docs); `hint` is the user's free-text framing when no subfolder matched. */
+export declare function buildDraftPrompt(feature: string, hint?: string): string;
+declare const EMPTY_INPUT_HINT = "No input docs found. Drop this feature's PRDs/specs in .d360-writer/input/<feature>/ (.md or .pdf), then run /draft.";
+/**
+ * Classic-REPL `/draft`: resolve the feature, then forward the draft-from-prd prompt to the agent.
+ * Multiple features + no selector → list them and ask (the TUI shows a picker; classic prints the list).
+ */
+export declare function draftCommand(args: string[], ctx?: ReplContext): Promise<SlashCommandResult>;
+export { EMPTY_INPUT_HINT };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "document360-writer",
-  "version": "0.4.53",
+  "version": "0.4.55",
   "description": "Standalone documentation agent CLI. Reads your code, writes your docs. Specialized for Document360 publishing.",
   "type": "module",
   "bin": {
@@ -34,7 +34,7 @@
     "@inquirer/prompts": "^8.4.3",
     "commander": "^14.0.3",
     "diff": "^8.0.4",
-    "document360-engine": "^0.2.30",
+    "document360-engine": "^0.2.32",
     "ink": "^5.2.1",
     "picocolors": "^1.1.1",
     "react": "^18.3.1",