@antoneeo/mkt-agentic-sdlc-skill 0.19.0 → 0.21.0

package/CHANGELOG.md

@@ -1,5 +1,21 @@
 # Changelog
 
+## [0.21.0] - 2026-10-18
+
+### Added
+- F-074: every Vision is born from an owner interview. Before any Vision text is written (project, feature, the MKT-VISION, and the devPNT M-VISION), the agent asks the owner six questions in order, re-asking an answer that has the wrong form: the problem as one concrete case, the benefit as a result for someone, the actors including who takes the initiative, a success signal with its starting value, the boundaries, and the known constraints with where each comes from. Then the owner approves a one- or two-sentence north star in their own words; without it no Vision is written, not even a draft. The blind check still tests that the rules hold; the approved north star shows they are the owner's. `vision.md` §The owner interview.
+
+### Changed
+- `elicitation.md`: the skip path never covers the MKT-VISION; Wave 1 gathers the facts, the interview gathers the Vision.
+- Bootstrap no longer writes a Vision reconstructed by the agent: the installer seeds `mkt_docs/vision/MKT_VISION.md` as a stub awaiting the interview (an existing file is never overwritten).
+- A Non-Goal now bounds scope. It rejects a proposal that pursues what it names; it is not a ban on behaviour that already exists and creates no obligation. A behaviour that must never happen is an Invariant or a constraint with its source.
+- The MKT_VISION template gains North Star and Problem, the actor with the initiative, signals with starting values, Non-Goals as scope, and the source of every constraint.
+
+## [0.20.0] - 2026-10-18
+
+### Added
+- F-072: `scripts/docs_site.py --root <project>` writes a static, read-only website of what the agent reads in the project: what it is (reading guide, Vision, rules, documents), its open work with each next step verbatim, and — with a knowledge base — a map of topics, the facts with the exact passage each comes from, what an inferred fact rests on, and the source documents. It opens from disk with the network off, writes outside the docs root, changes nothing in it, and selects, ranks or recommends nothing. Each analysis opens with the chain the agent works through — Vision, use cases, flows and interfaces, risks, solution study, design and tests, merge brief and E2E script, Diary — the Vision's North Star is shown above the home page, and the guides have a page of their own: the guide router, the operative guides with when to read each, and the code-comprehension guides. The chronology lists the dated events the documents declare (Diary entries, spike outcomes, request-record entries, review-log rows, decision records, dated project notes, notes and sources received), most recent first, read with the same F-073 readers `validate` uses. Shared by the four packages (generator, page and battery are byte-identical spine files).
+
 ## [0.19.0] - 2026-10-17
 
 ### Changed

package/README.md

@@ -27,6 +27,8 @@ Turns an AI agent into a disciplined marketing strategist that produces a profes
 3. **Adversarial CMO review** — an independent, fresh-context reviewer attacks the strategy before the user sees it (generic-positioning swap test, untraced claims, orphan tactics).
 4. **Verbatim request record** — every E3 engagement starts `audit/requests/REQUEST_[engagement].md` before Wave 1: the client's own words and every later decision, append-only and redacted for secrets; owner-given FACT rows and the plan cite its entries, and reviews check client statements against it.
 
+The **docs site** (`scripts/docs_site.py --root <project> [--open]`) writes a static, offline, read-only website of what the agent reads in the project — reading guide, Vision, rules, documents, open work with each next step, and, with a knowledge base, the topic map, each fact with its exact source passage, and the source documents. It is written outside the docs root (`mkt_docs/` or `ai_docs/`); nothing is ranked or recommended.
+
 The agent asks the user only for facts the user uniquely owns (product, price, budget, capacity); everything else — market sizing, competitor analysis, channel benchmarks — is derived from real web research.
 
 ## Install

package/gemini-extension.json

@@ -1,6 +1,6 @@
 {
   "name": "mkt-agentic-sdlc",
-  "version": "0.19.0",
+  "version": "0.21.0",
   "description": "Evidence-First marketing planning protocol with engagement triage, SOSTAC workflow, evidence ledger and optional devPNT integration.",
   "author": "Antonio Pinto (https://github.com/Antoneeo)"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@antoneeo/mkt-agentic-sdlc-skill",
-  "version": "0.19.0",
+  "version": "0.21.0",
   "description": "Evidence-First marketing planning protocol for Claude Code, Gemini CLI, Google Antigravity and Codex: engagement triage, SOSTAC workflow, evidence ledger, mechanical validator and optional devPNT integration.",
   "keywords": [
     "claude-code",
@@ -34,6 +34,11 @@
     "skills/mkt-agentic-sdlc/review.md",
     "skills/mkt-agentic-sdlc/scripts/sdlc_core.py",
     "skills/mkt-agentic-sdlc/scripts/knowledge.py",
+    "skills/mkt-agentic-sdlc/scripts/docs_site.py",
+    "skills/mkt-agentic-sdlc/docs_site/index.html",
+    "skills/mkt-agentic-sdlc/docs_site/app.js",
+    "skills/mkt-agentic-sdlc/docs_site/style.css",
+    "skills/mkt-agentic-sdlc/docs_site/strings.js",
     "skills/mkt-agentic-sdlc/memory.md",
     "skills/mkt-agentic-sdlc/routing.md",
     "skills/mkt-agentic-sdlc/guides.md",

package/skills/mkt-agentic-sdlc/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: mkt-agentic-sdlc
-version: 0.19.0
+version: 0.21.0
 description: Evidence-First marketing planning protocol with engagement triage, SOSTAC workflow, evidence ledger, adversarial CMO review, a complete Standalone mode and optional symbiosis with devPNT. Use for marketing plans, go-to-market strategy, campaign planning and market research.
 author: Antonio Pinto (https://github.com/Antoneeo)
 copyright: (c) 2026 Antonio Pinto
@@ -18,6 +18,7 @@ Support files in the skill directory:
 - `templates.md`: templates for every artifact and deliverable.
 - `review.md`: the family's shared review discipline (independence ladder, rounds, log). The marketing-specific attack surface — swap test, untraced numbers, orphan tactics, missing kill/scale — lives in `frameworks.md`'s falsification rules; the adversarial CMO review applies them through `review.md`'s procedure.
 - `scripts/mkt_check.py` + `scripts/sdlc_core.py`: the mechanical validator (`check`, `validate`, `ledger`, `benefit`, `budget`, `funnel`, `trace`, `index`, plus the spine's `stale`/`mark`/`gate`/`orient`/`plan`/`migrate`).  Keep the entry point, `scripts/sdlc_core.py` and `scripts/knowledge.py` together; the last supplies common memory and KB integrity.
+- `scripts/docs_site.py --root <project>`: writes an offline, read-only site of what the agent reads here, for the user to browse.
 - `hybrid.md`: the devPNT seam — the authoritative hierarchy, the ownership matrix (which artifact is mastered where), and the Hybrid rules. Read it when the `devpnt_*` tools point at this project; a Standalone engagement never needs it.
 - `ENFORCEMENT.md`: optional setup for CI and hooks.
 
@@ -85,7 +86,7 @@ One event, one destination: when the trigger fires and the document does not exi
 | `audit/HANDOFF_[engagement].md` | Session ends with that engagement unfinished AND there is volatile resume state. Ephemeral, deleted at closure. | 8 / 9 / session end |
 | `audit/reviews/REVIEW_LOG.md` | Every completed review — when and what to write is `review.md`; schema is `templates.md`. | 6 / 9 |
 | `reference/GUIDE_[topic].md` | Origin+purpose test (`guides.md`), or a proactive proposal the user accepted. | 8 / 9 |
-| `vision/` documents | Bootstrap as `Status: DRAFT`; promoted to APPROVED only by explicit user confirmation, and only after the blind check (`vision.md` §6). | 1 / 5 |
+| `vision/` documents | Bootstrap writes a **stub** awaiting the owner interview (`Status: DRAFT`) — never a Vision reconstructed by the agent; the Vision is written only after the owner interview and its approved north star (`vision.md` §The owner interview); promoted to APPROVED only by explicit user confirmation, and only after the blind check (`vision.md` §6). | 1 / 5 |
 
 ## Operating Modes
 
@@ -138,7 +139,7 @@ Deliverable language: ask for (or infer) the target market's language in Discove
 
 ### 2. Discovery (Situation — internal)
 - Run elicitation **Wave 1** (`elicitation.md`): business facts only, plain language, max 4 questions per round, options where a real choice exists.
-- Every fact captured becomes a `FACT` ledger entry whose source cites its request-record entry (`user, REQUEST_[engagement].md#R2`). Draft `MKT_VISION.md` (Status: DRAFT) from the answers.
+- Every fact captured becomes a `FACT` ledger entry whose source cites its request-record entry (`user, REQUEST_[engagement].md#R2`). Then run the owner interview (`vision.md` §The owner interview) — Wave 1 gathers the facts, the interview gathers the Vision — and draft `MKT_VISION.md` (Status: DRAFT) from its answers only after the north star is approved in the owner's words.
 - **Vision Gate:** the user approves the MKT-VISION (expected benefit, success signals, non-goals) before research spends effort. Hybrid: this is the devPNT M-VISION creation gate — vision first, then the milestone.
 
 ### 3. Research (Situation — external)