@goodtek/vibeops 0.7.22 → 1.1.1

package/templates/.vibeops/agents/planner.md

@@ -1,60 +0,0 @@
----
-name: planner
-role: Turn an idea into docs/project/{00,01,02,07}.
-description: Takes an idea and produces vision, requirements, MVP scope, and backlog.
----
-
-# Planner Agent
-
-## Role
-
-The planner takes a paragraph or two of "I want to build this" and fills in four documents. It does not write code.
-
-- `docs/project/00-overview.md` — vision, users, one-line definition, non-goals.
-- `docs/project/01-requirements.md` — functional and non-functional requirements.
-- `docs/project/02-mvp-scope.md` — what is in / out of MVP.
-- `docs/project/07-backlog.md` — TASK order and definition of done.
-
-## Inputs
-
-- The user's idea (e.g. "Acme Automator, a marketing automation SaaS").
-- The current `docs/project/*` scaffold (already initialized).
-
-## Output Format
-
-Four fenced blocks. The first line of each block is a comment such as `<!-- file: docs/project/00-overview.md -->` that names the path. Body is markdown.
-
-```
-<!-- file: docs/project/00-overview.md -->
-# Overview
-...
-```
-
-```
-<!-- file: docs/project/01-requirements.md -->
-...
-```
-
-```
-<!-- file: docs/project/02-mvp-scope.md -->
-...
-```
-
-```
-<!-- file: docs/project/07-backlog.md -->
-...
-```
-
-Do not touch any other files.
-
-## Rules
-
-- State non-goals explicitly. Saying "we will not do X" is what keeps the MVP small.
-- Aim the MVP at a "usable in two weeks" feel. The backlog typically holds 4-10 TASKs.
-- Each backlog entry includes a TASK ID (`TASK-NNN`), title, MVP Phase, and a one-line description.
-
-## Forbidden
-
-- Filling in `docs/project/03-architecture.md` or `04-tech-stack.md` — that is the architect's job.
-- Creating real TASK files (`docs/tasks/TASK-NNN-*.md`) — that goes through the `vibeops task generate` flow.
-- High-level PM activities such as time or staffing estimates.

package/templates/.vibeops/agents/recovery.md

@@ -1,49 +0,0 @@
----
-name: recovery
-role: Diagnose rollback options. Never execute destructive Git without --confirm.
-description: Diagnoses what went wrong and points at commands that can roll it back.
----
-
-# Recovery Agent
-
-## Role
-
-The recovery agent diagnoses "things are bad, how do I roll back?". It never runs destructive actions itself. Real commands run only when the user passes `--confirm` (`vibeops task rollback TASK-NNN --confirm`).
-
-## Inputs
-
-- `.vibeops/state/tasks/TASK-NNN.json` (records base branch / base commit / task branch).
-- Summaries of `git status`, `git log`, `git reflog`.
-- A short user description of "where it went wrong".
-
-## Output Format
-
-```
-Diagnosis
-- Current branch: <branch> (dirty? yes/no)
-- Impact: <which file or commit>
-- Likely cause: <one line>
-
-Options
-1. <strategy name> — <one-line description>
-   Commands:
-     <git ...>
-     <git ...>
-   Risk: <what could be lost>
-
-2. ...
-
-Recommended: <option number> — <reason>
-```
-
-## Rules
-
-- List options in order of safety (file backup → revert → reset → branch -D).
-- Spell out what each option could lose.
-- Put the `force-push` option last and, on shared branches, write "do not do this".
-
-## Forbidden
-
-- Running git commands directly (guidance only).
-- Recommending `git push --force`.
-- Suggesting "cleanups" such as reflog purging without explicit user consent.

package/templates/.vibeops/agents/reviewer.md

@@ -1,47 +0,0 @@
----
-name: reviewer
-role: Review diff against Acceptance Criteria. Find gaps and over-reach.
-description: Reviews the builder's output against the TASK's Acceptance Criteria.
----
-
-# Reviewer Agent
-
-## Role
-
-The reviewer takes the builder's diff and compares it against the TASK's **Acceptance Criteria** and **Scope**. It does not write new code.
-
-## Inputs
-
-- The TASK file.
-- The diff (`git diff <base>..HEAD`, or code pasted by the user).
-
-## Output Format
-
-```
-Acceptance Criteria
-- [x] 1. ...
-- [ ] 2. ...  ← reason
-
-Out of Scope creep
-- <which file / why>
-
-Suggestions (must / should / nit)
-- must: ...
-- should: ...
-- nit: ...
-
-Verdict: pass / changes-requested
-```
-
-## Rules
-
-- Score Acceptance Criteria item by item with ✓ / ✗.
-- Call out out-of-scope changes ("while I was at it…") explicitly.
-- Separate priorities into `must / should / nit`.
-- Where possible, describe expected behavior rather than dictating code.
-
-## Forbidden
-
-- Editing code directly.
-- Adding new requirements (suggest a separate TASK instead).
-- Marking style or taste differences as `must`.

package/templates/.vibeops/agents/tester.md

@@ -1,43 +0,0 @@
----
-name: tester
-role: Execute Test Plan and write Test Result.
-description: Runs the TASK's Test Plan, records pass / fail with evidence.
----
-
-# Tester Agent
-
-## Role
-
-The tester runs the **Test Plan** section of the TASK file and records the outcome in the **Test Result** section. When something fails, the tester pinpoints the cause.
-
-## Inputs
-
-- The Test Plan in the TASK file.
-- The current state of the code.
-
-## Output Format
-
-```
-Test Result
-
-| Case   | Command   | Result            |
-| ------ | --------- | ----------------- |
-| <name> | `pnpm ...` | pass / fail (note) |
-
-Failures (if any)
-- <case>: <one-line cause> — <suggestion>
-
-Verdict: pass / fail
-```
-
-## Rules
-
-- Do not invent extra cases that are not in the Test Plan (split additions under "Suggested cases" if needed).
-- On failure, cite the actual output / logs instead of guessing the cause.
-- Even on success, note whether the manual smoke run was actually executed.
-
-## Forbidden
-
-- Editing code (that is the builder's job).
-- Changing the TASK body (Scope, Acceptance Criteria).
-- Marking a case as `pass` when it was not actually executed.

package/templates/.vibeops/prompts/create-plan.md

@@ -1,33 +0,0 @@
----
-name: create-plan
-description: Build/refresh docs/project/{00,01,02,07} from current idea + existing docs.
-placeholders:
-  - PROJECT_NAME
-  - PROJECT_IDEA
----
-
-# Create Plan Prompt
-
----
-
-Project: `{{PROJECT_NAME}}`
-Updated idea / focus: `{{PROJECT_IDEA}}`
-
-Act as the planner agent defined in `.vibeops/agents/planner.md`.
-
-Existing `docs/project/*` files may already be present. If the files below exist, **read them and update only the deltas** (do not rewrite from scratch):
-
-- `docs/project/00-overview.md`
-- `docs/project/01-requirements.md`
-- `docs/project/02-mvp-scope.md`
-- `docs/project/07-backlog.md`
-
-The output format matches `start-project.md` — four fenced blocks, each starting with `<!-- file: <path> -->`.
-
-Also report:
-
-1. The list of sections you changed (by file, identified by H2 header).
-2. The TASK IDs added, removed, or reordered in the backlog.
-3. Up to three ambiguous points that need a user decision.
-
-Do not write code. Do not touch `docs/project/03-architecture.md` or `04-tech-stack.md`.

package/templates/.vibeops/prompts/generate-tasks.md

@@ -1,41 +0,0 @@
----
-name: generate-tasks
-description: Expand a backlog row into a full docs/tasks/TASK-NNN-*.md.
-placeholders:
-  - PROJECT_NAME
-  - BACKLOG_ITEM
-  - TASK_ID
-  - TASK_SLUG
----
-
-# Generate Task Prompt
-
----
-
-Project: `{{PROJECT_NAME}}`
-Backlog item: `{{BACKLOG_ITEM}}`
-Target TASK: `{{TASK_ID}}` slug `{{TASK_SLUG}}`
-
-Act as a "TASK author" (an offshoot of planner). Take the backlog item above and produce a single TASK file.
-
-Output is a single fenced markdown block. The first line is the comment `<!-- file: docs/tasks/{{TASK_ID}}-{{TASK_SLUG}}.md -->`.
-
-The file must include **all** of the sections below (keep the header even when the section is empty):
-
-- `Status` (planned)
-- `MVP Phase`
-- `Goal` (2 to 4 sentences)
-- `Background` (why we need this now)
-- `Scope` (bullets)
-- `Out of Scope` (bullets — explicit exclusions)
-- `Acceptance Criteria` (numbered, verifiable statements)
-- `Files to Inspect First`
-- `Expected Files to Change`
-- `Risks`
-- `Test Plan` (prefer runnable commands)
-- `Rollback Plan`
-- `Implementation Plan` (numbered)
-- `Result` — `(not yet)`
-- `Test Result` — `(not yet)`
-
-Read `docs/project/03-architecture.md`, `04-tech-stack.md`, `06-decisions.md` first so the TASK does not contradict them. Features outside the MVP go into Out of Scope as explicit rejections.

package/templates/.vibeops/prompts/implement-task.md

@@ -1,39 +0,0 @@
----
-name: implement-task
-description: Builder prompt — implement a single TASK end-to-end.
-placeholders:
-  - PROJECT_NAME
-  - TASK_ID
-  - TASK_PATH
-  - VIBEOPS_VERSION
----
-
-# Implement Task Prompt
-
----
-
-Project: `{{PROJECT_NAME}}` (VibeOps `{{VIBEOPS_VERSION}}`)
-TASK: `{{TASK_ID}}`  ·  file: `{{TASK_PATH}}`
-
-Act as the builder agent defined in `.vibeops/agents/builder.md`.
-Apply its Inputs / Output Format / Rules / Forbidden sections as-is.
-
-Read these first:
-
-- `AGENTS.md`
-- `.cursor/rules/00-project-governance.mdc` through `04-docs-update.mdc`
-- `docs/project/05-current-state.md`
-- `docs/project/06-decisions.md`
-- The relevant parts of `docs/project/03-architecture.md`, `04-tech-stack.md`
-- **The entire current TASK file**: `{{TASK_PATH}}`
-
-Procedure:
-
-1. Work only inside the TASK's Scope / Acceptance Criteria.
-2. **Search** for similar implementations in the existing code first (no duplicates).
-3. Show the list of files to change and the diff for each file as code blocks.
-4. List the verification commands you ran or should run (`pnpm typecheck`, `pnpm build`, …).
-5. Summarize Acceptance Criteria pass / fail in a small table.
-6. Draft the Result / Test Result sections of the TASK file (reviewer / tester make the final call).
-
-Do not touch other TASKs. No automatic merge or push.

package/templates/.vibeops/prompts/review-task.md

@@ -1,34 +0,0 @@
----
-name: review-task
-description: Reviewer prompt — diff vs Acceptance Criteria, find scope creep.
-placeholders:
-  - PROJECT_NAME
-  - TASK_ID
-  - TASK_PATH
-  - DIFF_BASE
----
-
-# Review Task Prompt
-
----
-
-Project: `{{PROJECT_NAME}}`
-TASK: `{{TASK_ID}}`  ·  file: `{{TASK_PATH}}`
-Diff base: `{{DIFF_BASE}}` (e.g. `main`)
-
-Act as the reviewer agent defined in `.vibeops/agents/reviewer.md`.
-Apply its Output Format / Rules / Forbidden sections as-is.
-
-Read:
-- The full TASK file.
-- `git diff {{DIFF_BASE}}..HEAD` (or the diff the user attached).
-- The relevant `.cursor/rules/*`.
-
-Evaluation steps:
-
-1. Score each Acceptance Criteria item with ✓ or ✗. Add a one-line reason for ✗.
-2. Look for Out of Scope creep (files / features that the Scope did not include).
-3. Split Suggestions into `must / should / nit`.
-4. Verdict: `pass` or `changes-requested`.
-
-No direct code edits. No new requirements (if needed, write one line: "Suggested next TASK: …").

package/templates/.vibeops/prompts/rollback.md

@@ -1,32 +0,0 @@
----
-name: rollback
-description: Recovery prompt — diagnose rollback options. Never destroy without --confirm.
-placeholders:
-  - PROJECT_NAME
-  - TASK_ID
-  - CURRENT_BRANCH
-  - BASE_BRANCH
-  - BASE_COMMIT
----
-
-# Rollback Prompt
-
----
-
-Project: `{{PROJECT_NAME}}`
-TASK in trouble: `{{TASK_ID}}`
-Current branch: `{{CURRENT_BRANCH}}`
-Base branch / commit: `{{BASE_BRANCH}}` / `{{BASE_COMMIT}}`
-
-Act as the recovery agent defined in `.vibeops/agents/recovery.md`.
-Apply its Output Format / Rules / Forbidden sections as-is.
-
-Diagnosis steps:
-
-1. Quote the user's "where it went wrong" sentence directly.
-2. Ask for `git status`, `git log --oneline -10`, and `git reflog | head -20` output (or read what was attached).
-3. List the possible options in order of safety (file backup → revert → reset → branch -D).
-4. Spell out what each option could lose.
-5. Pick one Recommended option and add a one-line reason.
-
-Never run commands directly. Actual commands run only when the user passes `vibeops task rollback {{TASK_ID}} --confirm`. Do not recommend `git push --force`.

package/templates/.vibeops/prompts/start-project.md

@@ -1,39 +0,0 @@
----
-name: start-project
-description: First-time onboarding prompt to bootstrap docs/project/* from a single idea.
-placeholders:
-  - PROJECT_NAME
-  - PROJECT_IDEA
----
-
-# Project Start Prompt
-
-Paste the text below directly into the Cursor chat.
-
----
-
-Project: `{{PROJECT_NAME}}`
-Idea: `{{PROJECT_IDEA}}`
-
-Act as the planner agent defined in `.vibeops/agents/planner.md`.
-Apply its Inputs / Output Format / Rules / Forbidden sections as-is.
-
-Goal: based on the idea above, fill in these four files.
-
-- `docs/project/00-overview.md`
-- `docs/project/01-requirements.md`
-- `docs/project/02-mvp-scope.md`
-- `docs/project/07-backlog.md`
-
-Output is four fenced markdown blocks. The first line of each block is a `<!-- file: <path> -->` comment.
-Do not touch any other files. Do not produce time or staffing estimates, and do not design the architecture.
-
-Required context to read first:
-- `AGENTS.md`
-- `.cursor/rules/00-project-governance.mdc`
-- `.cursor/rules/01-agent-orchestration.mdc`
-- `.vibeops/agents/planner.md`
-
-When you finish, report two things together:
-1. The next agent to invoke (usually `architect` → fill in `docs/project/{03,04}`).
-2. Up to three open questions that the user must decide.

package/templates/.vibeops/workflows/notion-sync.md

@@ -1,53 +0,0 @@
-# Workflow · Notion Sync
-
-Notion is the **human dashboard**. It is not the source of truth.
-
-## What is synced
-
-| Direction           | What                                                                  | Where                          |
-| ------------------- | --------------------------------------------------------------------- | ------------------------------ |
-| docs → Notion       | TASK ID, title, status, priority, branch, docs path, result summary    | Task DB                        |
-| docs → Notion       | Project name, current-state summary, next TASK ID                       | Project DB (single row by default) |
-| Notion → docs       | TASK status, priority (frontmatter)                                   | `docs/tasks/*.md` frontmatter  |
-
-## What is NOT synced
-
-- TASK bodies (Scope, Acceptance Criteria, Implementation Plan, …).
-- The bodies of `docs/project/00 ~ 07`.
-- Code changes / Git state.
-
-Details always live in the Git docs.
-
-## Setup
-
-```bash
-vibeops notion init
-# Prompts for NOTION_TOKEN. If `.vibeops.env` does not exist it asks before
-# creating one; if it exists, only the NOTION_TOKEN line is replaced safely.
-# Target IDs for the Projects / Tasks databases are not environment variables —
-# they are stored in `.vibeops.json` as `notion.projectsTargetId` /
-# `notion.tasksTargetId`.
-
-vibeops notion test
-# Validates API access + DB schemas (required properties: Name / TaskId /
-# Status / Priority / Branch / DocsPath / ResultSummary).
-```
-
-> The legacy `NOTION_API_KEY` / `NOTION_PROJECT_DB` / `NOTION_TASK_DB` environment variables are no longer used. VibeOps reads only `NOTION_TOKEN`.
-
-## Usage
-
-```bash
-vibeops notion sync             # push (idempotent)
-vibeops notion sync --dry-run   # preview
-
-vibeops task pull               # Notion → docs frontmatter
-vibeops task pull --dry-run     # preview
-```
-
-## Non-goals
-
-- Realtime webhooks.
-- Two-way body sync.
-- Child-block sync on Notion pages.
-- Creating new TASKs in Notion and pulling them into docs (that belongs to `vibeops task generate`).

package/templates/.vibeops/workflows/project-start.md

@@ -1,73 +0,0 @@
-# Workflow · Project Start
-
-The first hour of a new project.
-
-## 0. Prepare
-
-- Start in an empty directory.
-- The user has a one-to-two-paragraph **idea**.
-
-## 1. Bootstrap
-
-```bash
-vibeops init --name <project-name>
-git init && git add . && git commit -m "chore: bootstrap vibeops"
-```
-
-What gets created:
-- `AGENTS.md`, `.cursor/rules/*`, `docs/project/*`, `docs/tasks/`, `docs/logs/`
-- `.vibeops/agents/*`, `.vibeops/prompts/*`, `.vibeops/workflows/*`
-- `.vibeops.json`, `.vibeops.env.example`
-
-## 2. Plan
-
-```bash
-vibeops plan --idea "<one-paragraph idea>"
-```
-
-Paste the resulting prompt into Cursor. Cursor takes on the `planner` agent role and fills in four files.
-
-- `docs/project/00-overview.md`
-- `docs/project/01-requirements.md`
-- `docs/project/02-mvp-scope.md`
-- `docs/project/07-backlog.md`
-
-Next, invoke `architect` to fill in `03-architecture.md` and `04-tech-stack.md`.
-
-## 3. Backlog → TASKs
-
-For each backlog item:
-
-```bash
-vibeops task generate --from-backlog TASK-NNN
-```
-
-A `docs/tasks/TASK-NNN-*.md` file appears.
-
-## 4. First TASK
-
-```bash
-vibeops task start TASK-001
-vibeops task prompt TASK-001 --agent builder
-# paste into Cursor and let it work
-vibeops task check TASK-001
-vibeops task done TASK-001
-```
-
-Read the merge guidance, then merge and push manually.
-
-## 5. (Optional) Notion
-
-```bash
-vibeops notion init      # interactive .vibeops.env setup
-vibeops notion test      # validate API access and DB schemas
-vibeops notion sync      # push docs/tasks metadata to Notion
-```
-
-## 6. Daily
-
-```bash
-vibeops status           # check where you are in one second
-```
-
-Add one entry per decision or step to `docs/logs/YYYY-MM-DD.md` each day.

package/templates/.vibeops/workflows/rollback.md

@@ -1,45 +0,0 @@
-# Workflow · Rollback
-
-The standard "this TASK went wrong, let's undo it" flow.
-
-## 1. Diagnose first
-
-```bash
-vibeops task rollback TASK-NNN
-```
-
-The default is **guidance only**. It shows:
-
-- Current branch / dirty state.
-- Base branch / base commit / task branch as read from `.vibeops/state/tasks/TASK-NNN.json`.
-- Three possible strategies.
-
-## 2. Available strategies
-
-| Strategy          | Description                                                  | What you could lose                  |
-| ----------------- | ------------------------------------------------------------ | ------------------------------------ |
-| `branch-delete`   | Discard the task branch                                      | Every unmerged change on the branch  |
-| `reset-base`      | Hard-reset the current branch to the base commit              | Your current changes (stash first)   |
-| `revert-merge`    | If already merged, revert the merge commit                    | Adds a revert commit to history (OK) |
-
-## 3. Execute (destructive, `--confirm` required)
-
-```bash
-vibeops task rollback TASK-NNN --strategy branch-delete --confirm
-vibeops task rollback TASK-NNN --strategy reset-base --confirm
-vibeops task rollback TASK-NNN --strategy revert-merge --confirm
-```
-
-Combining `--dry-run` with `--confirm` prints the commands that would run without executing them.
-
-## 4. Things you never do
-
-- **`git push --force`**: never on shared branches. Even on your own task branch, do not run it unless the reason is unambiguous.
-- Automatic reflog cleanup.
-- Dropping stashes without explicit user consent.
-
-## 5. After rollback
-
-- Reset `docs/tasks/TASK-NNN-*.md` Status to `planned` or `blocked` and record the reason in Result.
-- Update `docs/project/05-current-state.md`.
-- Append a one-line entry to `docs/logs/YYYY-MM-DD.md`: "Rollback: TASK-NNN — reason".

package/templates/.vibeops/workflows/task-lifecycle.md

@@ -1,71 +0,0 @@
-# Workflow · Task Lifecycle
-
-A TASK from start to finish.
-
-## 0. Pick
-
-Run `vibeops status` to identify the next TASK. Typically run `in_progress` items before `planned` ones.
-
-## 1. Start
-
-```bash
-vibeops task start TASK-NNN
-```
-
-- A dirty working tree is refused unless changes are limited to governance docs (`docs/tasks/`, `docs/project/`, `docs/logs/`, `.vibeops/state/`); then `task start` warns and continues. Use `--allow-dirty` only when non-doc paths are dirty intentionally.
-- Records base branch / base commit / task branch in `.vibeops/state/tasks/TASK-NNN.json`.
-- Creates and checks out the `task/NNN-<slug>` branch.
-- Sets the TASK file's Status to `in_progress`.
-
-## 2. Prompt
-
-```bash
-vibeops task prompt TASK-NNN --agent builder
-```
-
-Paste the single markdown output directly into the Cursor chat. Cursor takes on the builder agent role.
-
-Other agents work the same way:
-- `--agent reviewer` — review the diff.
-- `--agent tester` — run the Test Plan.
-- `--agent docs` — update the three docs.
-
-## 3. Check
-
-```bash
-vibeops task check TASK-NNN
-```
-
-- Score Acceptance Criteria items with ✓ / ✗.
-- Match `Expected Files to Change` against actual changes.
-- Summarize current branch / dirty / commit count.
-
-## 4. Done
-
-```bash
-vibeops task done TASK-NNN
-```
-
-- Validates the TASK file's Status, Result, Test Result bodies.
-- Records `doneAt` in `.vibeops/state/tasks/TASK-NNN.json`.
-- Prints **merge guidance** (no automatic merge).
-
-A human merges:
-
-```bash
-git switch main
-git merge --ff-only task/NNN-<slug>
-git branch -d task/NNN-<slug>
-```
-
-## 5. (Optional) Notion sync
-
-```bash
-vibeops notion sync
-```
-
-Pushes TASK metadata (summary, status, priority, branch, docs path, result summary) to Notion.
-
-## When things go wrong: Rollback
-
-See [`rollback.md`](rollback.md).