@jonit-dev/night-watch-cli 1.8.3 → 1.8.4-beta.1

package/dist/templates/skills/nw-create-prd.md

@@ -0,0 +1,61 @@
+# Skill: nw-create-prd
+
+Create a new Product Requirements Document (PRD) for Night Watch to implement autonomously.
+
+## When to use
+
+When the user describes a feature, bug fix, or improvement they want Night Watch to implement.
+
+## Steps
+
+1. **Gather requirements** — if not fully described, ask:
+   - What problem does this solve?
+   - What is the expected outcome?
+
+2. **Assess complexity**:
+   - **1 (Simple)**: single-file fix, minor config change, small bug
+   - **2 (Medium)**: multi-file feature, new endpoint, new component
+   - **3 (Complex)**: new subsystem, architectural change, major refactor
+
+3. **Split into phases** — each phase should be an independently testable checkpoint:
+   - Phase 1: data models, interfaces, schema
+   - Middle phases: services, API, core logic
+   - Final phase: UI, integration, tests
+
+4. **Write the PRD** to `docs/prds/<kebab-case-title>.md` using this structure:
+
+```
+# PRD: <Title>
+
+**Complexity: <1|2|3> → <Simple|Medium|Complex> mode**
+
+## Problem
+
+<1-2 sentences describing the user problem or business need>
+
+## Solution
+
+- <bullet 1>
+- <bullet 2>
+- <bullet 3>
+
+## Phases
+
+### Phase 1: <Name>
+
+- [ ] <specific implementation task>
+- [ ] <write tests for above>
+
+### Phase 2: <Name>
+
+- [ ] <specific implementation task>
+- [ ] <write integration tests>
+
+## Acceptance Criteria
+
+- [ ] All phases complete
+- [ ] All tests pass
+- [ ] Feature reachable from existing code (no orphaned code)
+```
+
+5. **Confirm** to the user: show the file path and remind them to run `night-watch run` to execute immediately, or it will run on the next scheduled cron cycle.

package/dist/templates/skills/nw-review.md

@@ -0,0 +1,39 @@
+# Skill: nw-review
+
+Run the Night Watch automated PR reviewer on open pull requests.
+
+## When to use
+
+When the user wants to trigger automated code review on Night Watch PRs, or when a PR needs a review score.
+
+## Steps
+
+1. **List open Night Watch PRs**:
+
+   ```
+   gh pr list --state open --json number,title,headRefName --jq '.[] | select(.headRefName | startswith("night-watch/"))'
+   ```
+
+2. **Run the reviewer** (processes all eligible PRs):
+
+   ```
+   night-watch review
+   ```
+
+3. **Review a specific PR**:
+
+   ```
+   night-watch review --pr <number>
+   ```
+
+4. **Check review results**:
+   ```
+   night-watch logs --type review
+   ```
+
+## Notes
+
+- Minimum passing score: 80/100 (configurable via `minReviewScore` in `night-watch.config.json`)
+- Failed reviews block auto-merge and trigger webhook notifications
+- The reviewer runs automatically on its own cron schedule (`reviewerSchedule` in config)
+- Review checks: code quality, test coverage, PR description, acceptance criteria alignment

package/dist/templates/skills/nw-run.md

@@ -0,0 +1,39 @@
+# Skill: nw-run
+
+Manually trigger Night Watch to execute the next available PRD immediately.
+
+## When to use
+
+When the user wants to run Night Watch now instead of waiting for the cron schedule.
+
+## Steps
+
+1. **Check what's queued**:
+
+   ```
+   night-watch prd list
+   ```
+
+2. **Run the executor**:
+
+   ```
+   night-watch run
+   ```
+
+3. **To run a specific PRD** by filename:
+
+   ```
+   night-watch run --prd <filename.md>
+   ```
+
+4. **Monitor logs** in real time:
+   ```
+   night-watch logs --follow
+   ```
+
+## Notes
+
+- Night Watch executes ONE PRD per run to prevent timeouts and reduce risk
+- The automated cron schedule runs on a configurable interval (check with `night-watch status`)
+- Use `night-watch queue` to see all queued PRDs in priority order
+- If a run fails, the PRD is NOT marked as done — fix the issue and re-run

package/dist/templates/skills/nw-slice.md

@@ -0,0 +1,33 @@
+# Skill: nw-slice
+
+Slice a high-level roadmap item or epic into multiple focused PRD files for Night Watch execution.
+
+## When to use
+
+When the user has a large feature or roadmap item that should be broken into smaller,
+independently-executable pieces.
+
+## Steps
+
+1. **Ask for the epic description** if not provided.
+
+2. **Run the slicer** to auto-generate PRDs from a roadmap file:
+
+   ```
+   night-watch slice
+   ```
+
+   This reads `docs/roadmap.md` (or configured roadmap path) and generates PRD files.
+
+3. **To slice a specific feature**, first add it to `docs/roadmap.md`, then run slice.
+
+4. **Review generated PRDs** in `docs/prds/` — adjust scope, complexity, or phases if needed.
+
+5. PRDs run in creation order (or by `prdPriority` config) on the next Night Watch execution.
+
+## Tips
+
+- Each PRD should be deployable independently without breaking anything
+- Keep PRDs focused on 1-2 user stories for faster execution
+- Complex PRDs (score 3) often benefit from splitting into 2 medium PRDs
+- Use `Depends-On: <other-prd.md>` in a PRD's front matter to enforce ordering

package/dist/templates/skills/skills/_codex-block.md

@@ -0,0 +1,58 @@
+## Night Watch Skills
+
+The following Night Watch CLI commands are available. Use them when the user asks to manage PRDs, board issues, or trigger Night Watch operations.
+
+### Create a PRD (`/nw-create-prd`)
+
+Create a new PRD at `docs/prds/<name>.md`. Ask for feature title, assess complexity (1=Simple, 2=Medium, 3=Complex), split into phases with checkbox tasks, then write the file. Tell the user to run `night-watch run` to execute immediately.
+
+### Add Issue to Board (`/nw-add-issue`)
+
+Add a GitHub issue to the Night Watch board:
+
+```
+night-watch board add-issue <issue-number>
+night-watch board add-issue <issue-number> --column "In Progress"
+```
+
+Available columns: Draft, Ready, In Progress, Review, Done.
+
+### Run Next PRD (`/nw-run`)
+
+Manually trigger Night Watch to execute the next PRD:
+
+```
+night-watch prd list         # see what's queued
+night-watch run              # execute next PRD
+night-watch run --prd <file> # run specific PRD
+night-watch logs --follow    # monitor progress
+```
+
+### Slice Roadmap (`/nw-slice`)
+
+Break a high-level feature into multiple PRD files:
+
+```
+night-watch slice
+```
+
+Reads `docs/roadmap.md` and generates PRDs. Review and adjust output in `docs/prds/`.
+
+### Sync Board (`/nw-board-sync`)
+
+Sync the GitHub board with PRD/PR state:
+
+```
+night-watch board status
+night-watch board sync
+```
+
+### Review PRs (`/nw-review`)
+
+Run automated PR review:
+
+```
+night-watch review
+night-watch review --pr <number>
+night-watch logs --type review
+```

package/dist/templates/skills/skills/nw-add-issue.md

@@ -0,0 +1,39 @@
+# Skill: nw-add-issue
+
+Add an existing GitHub issue to the Night Watch project board for tracking and execution.
+
+## When to use
+
+When the user wants to add a GitHub issue to the Night Watch Kanban board.
+
+## Steps
+
+1. **Check for issue number** — if not provided, list open issues:
+
+   ```
+   gh issue list --state open --limit 20
+   ```
+
+   Ask the user which issue(s) to add.
+
+2. **Add the issue to the board**:
+
+   ```
+   night-watch board add-issue <issue-number>
+   ```
+
+3. **Optionally specify a column** (default: "Ready"):
+
+   ```
+   night-watch board add-issue <issue-number> --column "In Progress"
+   ```
+
+   Available columns: `Draft`, `Ready`, `In Progress`, `Review`, `Done`
+
+4. **Confirm** the issue was added and show its board position.
+
+## Notes
+
+- Issues in "Ready" are picked up automatically by Night Watch on the next run
+- Move issues to "Draft" if they're not yet ready for autonomous execution
+- Use `night-watch board sync` if the board gets out of sync with PRDs

package/dist/templates/skills/skills/nw-board-sync.md

@@ -0,0 +1,47 @@
+# Skill: nw-board-sync
+
+Sync the GitHub Project board with the current state of Night Watch PRDs and pull requests.
+
+## When to use
+
+When the board is out of sync with PRD/PR status, or after manual changes to issues or PRDs.
+
+## Steps
+
+1. **View current board state**:
+
+   ```
+   night-watch board status
+   ```
+
+2. **Sync board with PRD filesystem**:
+
+   ```
+   night-watch board sync
+   ```
+
+3. **List open issues that may need board assignment**:
+
+   ```
+   gh issue list --state open --label "night-watch"
+   ```
+
+4. **Add any missing issues to the board**:
+   ```
+   night-watch board add-issue <number>
+   ```
+
+## Board Columns
+
+| Column      | Meaning                                          |
+| ----------- | ------------------------------------------------ |
+| Draft       | Not ready for execution                          |
+| Ready       | Queued for Night Watch — picked up automatically |
+| In Progress | Currently being implemented                      |
+| Review      | PR opened, awaiting review                       |
+| Done        | Merged and complete                              |
+
+## Notes
+
+- Night Watch auto-moves issues from Ready → In Progress when starting, and In Progress → Review when opening a PR
+- Use `night-watch board setup` to create the board if it doesn't exist yet

package/dist/templates/skills/skills/nw-create-prd.md

@@ -0,0 +1,61 @@
+# Skill: nw-create-prd
+
+Create a new Product Requirements Document (PRD) for Night Watch to implement autonomously.
+
+## When to use
+
+When the user describes a feature, bug fix, or improvement they want Night Watch to implement.
+
+## Steps
+
+1. **Gather requirements** — if not fully described, ask:
+   - What problem does this solve?
+   - What is the expected outcome?
+
+2. **Assess complexity**:
+   - **1 (Simple)**: single-file fix, minor config change, small bug
+   - **2 (Medium)**: multi-file feature, new endpoint, new component
+   - **3 (Complex)**: new subsystem, architectural change, major refactor
+
+3. **Split into phases** — each phase should be an independently testable checkpoint:
+   - Phase 1: data models, interfaces, schema
+   - Middle phases: services, API, core logic
+   - Final phase: UI, integration, tests
+
+4. **Write the PRD** to `docs/prds/<kebab-case-title>.md` using this structure:
+
+```
+# PRD: <Title>
+
+**Complexity: <1|2|3> → <Simple|Medium|Complex> mode**
+
+## Problem
+
+<1-2 sentences describing the user problem or business need>
+
+## Solution
+
+- <bullet 1>
+- <bullet 2>
+- <bullet 3>
+
+## Phases
+
+### Phase 1: <Name>
+
+- [ ] <specific implementation task>
+- [ ] <write tests for above>
+
+### Phase 2: <Name>
+
+- [ ] <specific implementation task>
+- [ ] <write integration tests>
+
+## Acceptance Criteria
+
+- [ ] All phases complete
+- [ ] All tests pass
+- [ ] Feature reachable from existing code (no orphaned code)
+```
+
+5. **Confirm** to the user: show the file path and remind them to run `night-watch run` to execute immediately, or it will run on the next scheduled cron cycle.

package/dist/templates/skills/skills/nw-review.md

@@ -0,0 +1,39 @@
+# Skill: nw-review
+
+Run the Night Watch automated PR reviewer on open pull requests.
+
+## When to use
+
+When the user wants to trigger automated code review on Night Watch PRs, or when a PR needs a review score.
+
+## Steps
+
+1. **List open Night Watch PRs**:
+
+   ```
+   gh pr list --state open --json number,title,headRefName --jq '.[] | select(.headRefName | startswith("night-watch/"))'
+   ```
+
+2. **Run the reviewer** (processes all eligible PRs):
+
+   ```
+   night-watch review
+   ```
+
+3. **Review a specific PR**:
+
+   ```
+   night-watch review --pr <number>
+   ```
+
+4. **Check review results**:
+   ```
+   night-watch logs --type review
+   ```
+
+## Notes
+
+- Minimum passing score: 80/100 (configurable via `minReviewScore` in `night-watch.config.json`)
+- Failed reviews block auto-merge and trigger webhook notifications
+- The reviewer runs automatically on its own cron schedule (`reviewerSchedule` in config)
+- Review checks: code quality, test coverage, PR description, acceptance criteria alignment

package/dist/templates/skills/skills/nw-run.md

@@ -0,0 +1,39 @@
+# Skill: nw-run
+
+Manually trigger Night Watch to execute the next available PRD immediately.
+
+## When to use
+
+When the user wants to run Night Watch now instead of waiting for the cron schedule.
+
+## Steps
+
+1. **Check what's queued**:
+
+   ```
+   night-watch prd list
+   ```
+
+2. **Run the executor**:
+
+   ```
+   night-watch run
+   ```
+
+3. **To run a specific PRD** by filename:
+
+   ```
+   night-watch run --prd <filename.md>
+   ```
+
+4. **Monitor logs** in real time:
+   ```
+   night-watch logs --follow
+   ```
+
+## Notes
+
+- Night Watch executes ONE PRD per run to prevent timeouts and reduce risk
+- The automated cron schedule runs on a configurable interval (check with `night-watch status`)
+- Use `night-watch queue` to see all queued PRDs in priority order
+- If a run fails, the PRD is NOT marked as done — fix the issue and re-run

package/dist/templates/skills/skills/nw-slice.md

@@ -0,0 +1,33 @@
+# Skill: nw-slice
+
+Slice a high-level roadmap item or epic into multiple focused PRD files for Night Watch execution.
+
+## When to use
+
+When the user has a large feature or roadmap item that should be broken into smaller,
+independently-executable pieces.
+
+## Steps
+
+1. **Ask for the epic description** if not provided.
+
+2. **Run the slicer** to auto-generate PRDs from a roadmap file:
+
+   ```
+   night-watch slice
+   ```
+
+   This reads `docs/roadmap.md` (or configured roadmap path) and generates PRD files.
+
+3. **To slice a specific feature**, first add it to `docs/roadmap.md`, then run slice.
+
+4. **Review generated PRDs** in `docs/prds/` — adjust scope, complexity, or phases if needed.
+
+5. PRDs run in creation order (or by `prdPriority` config) on the next Night Watch execution.
+
+## Tips
+
+- Each PRD should be deployable independently without breaking anything
+- Keep PRDs focused on 1-2 user stories for faster execution
+- Complex PRDs (score 3) often benefit from splitting into 2 medium PRDs
+- Use `Depends-On: <other-prd.md>` in a PRD's front matter to enforce ordering