@groupby/ai-dev 0.2.0 → 0.2.3

package/teams/teams/brain-studio/skills/code-review/SKILL.md

@@ -1,46 +0,0 @@
----
-name: 'code-review'
-description: 'Perform a standardized code review on the current changes. Use this when needing to evaluate how well the code matches our architecture docs, code quality, and so on.'
-allowed-tools:
-  - execute/runInTerminal
-  - edit/editFiles
-  - edit/createFile
-  - atlassian-rovo/*
----
-
-# Brain Studio — Code Review
-
-## Setup
-
-1. Use #tool:execute/runInTerminal to run `git diff origin/main...HEAD`. If that yields nothing, fall back to `git diff HEAD`. Use this output as the set of changes under review.
-2. Use #tool:execute/runInTerminal to run `git branch --show-current` and extract the Jira ticket key from the branch name (e.g. `BS-1056` from `BS-1056-my-feature`). If a ticket key is found, use the Atlassian Rovo MCP to fetch the issue and use its description and acceptance criteria to evaluate whether the code fulfils the ticket's intent.
-3. Inspect the diff to understand what types of changes are involved.
-4. Apply the **Doc Routing Table** in `.github/copilot-instructions.md` — use the change types you identified to determine which architecture docs to load. Use those docs as your source of truth throughout the review.
-5. If the codebase contradicts the docs, the **docs represent the target state** — flag the discrepancy rather than normalising the legacy pattern.
-
----
-
-## Review
-
-Evaluate the changes across these areas. Let the loaded architecture docs govern the specific standards — do not invent rules not found there.
-
-1. **Code Quality** — single responsibility principle, clarity, naming, redundancy, complexity, consistency with documented patterns
-2. **Regressions** — silent breakage, unexpected behaviour changes, altered logic outside of the stated scope of the ticket, downstream impact
-3. **Security** — input validation, sensitive data handling, auth correctness
-4. **Performance** — inefficient or unnecessarily expensive code, unnecessary re-renders, missing cleanups, over-importing
-5. **Error handling** — async error paths covered, error messaging in place, graceful degradation, no swallowed errors
-6. **Accessibility** — semantic HTML, ARIA attributes, keyboard navigation, focus management
-7. **Testing** — coverage of new logic, edge cases, error paths; flag superfluous tests
-8. **Documentation** — non-obvious logic commented; JSDoc updated where needed, architecture docs updated if the change introduces a new pattern or deviates from existing ones
-
----
-
-## Output Format
-
-- **Inline comments** for specific lines or blocks.
-- **Top-level observations** for broad themes or praise.
-- Prioritise by severity: 🔴 blocking / 🟡 important / 🔵 minor.
-- Do **not** include your reasoning steps or to-do list.
-- Close with a witty quatrain summarising the PR. 🎭
-
-Save the review to `docs/code-reviews/<branch-name>-code-review.md` (use the full branch name from Setup step 2). Confirm the file has been written.

package/toolsets/toolsets/rzlv-flow/README.md

@@ -1,102 +0,0 @@
-# rzlv-flow: Atlassian Intelligence Skills
-
-A toolset of modular, composable skills for Jira and Confluence developer workflows. Covers daily triage, ticket focus, wrap/sync, sprint status, context loading, and more — all without requiring the full BMAD Method or the rzlv-flow monolith.
-
-Each skill is standalone and can be installed individually or as a complete suite.
-
-## Quick Start
-
-```bash
-# 1. Install all skills + resources
-npx @groupby/ai-dev install toolset rzlv-flow
-
-# 2. Configure Atlassian MCP (see docs/mcp-setup.md)
-#    Add atlassian-rovo config to .vscode/mcp.json
-
-# 3. Use — ask your AI assistant:
-#    "Start my day"           → daily triage
-#    "Focus on PROJ-123"      → ticket deep-dive
-#    "Wrap up PROJ-123"       → wrap & sync
-```
-
-See [docs/getting-started.md](docs/getting-started.md) for a full walkthrough.
-
-## Skills
-
-| Skill | Description | Status |
-|-------|-------------|--------|
-| `jira-daily-triage` | Start-of-day ticket triage with sprint detection | Complete |
-| `jira-ticket-focus` | Deep-load a ticket with full context | Complete |
-| `jira-wrap-sync` | Wrap up work, draft comment, multi-action sync | Complete |
-| `jira-ticket-trace` | Trace code back to Jira requirements | Complete |
-| `jira-comment` | Add a comment to a Jira ticket with FCMP safety | Complete |
-| `jira-status` | Change ticket status with transition validation | Complete |
-| `jira-sprint-status` | Sprint status report with completion metrics | Complete |
-| `jira-sync` | Force-sync local Jira context with remote state | Complete |
-| `atlassian-orchestrator` | Pull surrounding ticket context and create structures | Complete |
-| `context-analyst` | Transform meeting transcripts into structured docs | Complete |
-| `confluence-publish` | Publish local markdown to Confluence with Leaf Bundle mirrors | Complete |
-| `confluence-fetch` | Pull a Confluence page into a local markdown mirror | Complete |
-
-> **Note:** `confluence-publish` provides lightweight ad-hoc publishing to Confluence. For bulk structured sync of `_docs/` folders following epic hierarchy, use `atlassian-orchestrator` Mode 3 instead.
-
-## Prerequisites
-
-### Required: Atlassian MCP (`atlassian-rovo`)
-
-All Jira and Confluence skills require the Atlassian MCP server for API access to your Atlassian instance.
-
-### Optional: GitHub MCP
-
-Only needed for PR creation features in `jira-wrap-sync`. Not required for any other skills.
-
-See [docs/mcp-setup.md](docs/mcp-setup.md) for detailed setup instructions.
-
-## Installation
-
-```bash
-npx @groupby/ai-dev install toolset rzlv-flow       # All skills + resources
-npx @groupby/ai-dev install skill jira-daily-triage   # Individual skill
-```
-
-Common options:
-
-| Flag | Description |
-|------|-------------|
-| `--target <dir>` | Install into a specific directory (defaults to cwd) |
-| `--dry-run` | Preview what would be installed without writing files |
-| `--force` | Overwrite existing files without prompting |
-| `--skip-existing` | Skip files that already exist |
-
-You can also copy skills manually from this repository into `docs/ai/skills/` and resources into `docs/ai/resources/`.
-
-## BMAD Compatibility
-
-These skills are compatible with BMAD's Jira file structure (`docs/jira/{instance}/{project}/...`) but do **not** require BMAD. They were originally developed as part of the BMAD "Atlassian Intelligence Suite" and have been extracted as standalone skills. If BMAD is installed in your project, these skills coexist without conflict.
-
-## Shared Resources
-
-Skills reference shared resource files installed to `docs/ai/resources/` in your project:
-
-| Resource | Description |
-|----------|-------------|
-| `fcmp-protocol.md` | Fetch-Compare-Merge-Push sync pattern for safe Atlassian read/write |
-| `jira-file-structure.md` | Standard directory layout for local Jira mirrors |
-| `confluence-file-structure.md` | Leaf Bundle pattern for Confluence page mirrors |
-| `sync-state-format.md` | YAML frontmatter schema for ticket and page files |
-| `confluence-page-templates/` | Starter scaffolds for Confluence pages (initiative overview, strategic context, technical architecture, decisions) |
-
-## MCP Setup Automation
-
-MCP server configuration is currently manual — see [docs/mcp-setup.md](docs/mcp-setup.md) for step-by-step instructions (~5 minutes). Automated MCP configuration via the CLI is a future enhancement.
-
-## Documentation
-
-| Doc | Description |
-|-----|-------------|
-| [docs/getting-started.md](docs/getting-started.md) | Quick walkthrough: install → configure → use |
-| [docs/mcp-setup.md](docs/mcp-setup.md) | Atlassian and GitHub MCP server configuration |
-
-## Contributing
-
-See the [architecture documentation](../../docs/architecture/README.md) for repo structure, skill authoring guides, and conventions.

package/toolsets/toolsets/rzlv-flow/docs/mcp-setup.md

@@ -1,126 +0,0 @@
-# MCP Server Setup Guide
-
-This guide covers configuring the MCP servers required by rzlv-flow skills.
-
----
-
-## Atlassian MCP (`atlassian-rovo`) — Required
-
-All Jira and Confluence skills depend on the Atlassian MCP server for API access.
-
-### VS Code Configuration
-
-Add the following to your `.vscode/mcp.json` (create the file if it doesn't exist):
-
-```json
-{
-  "servers": {
-    "atlassian-rovo": {
-      "command": "npx",
-      "args": ["-y", "@anthropic/atlassian-rovo-mcp"],
-      "env": {
-        "ATLASSIAN_SITE": "your-company.atlassian.net",
-        "ATLASSIAN_EMAIL": "you@company.com",
-        "ATLASSIAN_API_TOKEN": "${input:atlassianApiToken}"
-      }
-    }
-  },
-  "inputs": [
-    {
-      "type": "promptString",
-      "id": "atlassianApiToken",
-      "description": "Atlassian API Token",
-      "password": true
-    }
-  ]
-}
-```
-
-### Generating an API Token
-
-1. Go to [https://id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens)
-2. Click **Create API token**
-3. Give it a label (e.g. "VS Code MCP")
-4. Copy the generated token — you won't see it again
-
-### Verifying the Connection
-
-After configuring, ask the LLM to run a simple query:
-
-> "Search Jira for my open tickets using the Atlassian MCP"
-
-If the MCP server is configured correctly, it will call `mcp_atlassian-rovo_search` and return results. If you get an authentication error, double-check your site URL, email, and API token.
-
----
-
-## GitHub MCP — Optional
-
-Only needed for PR creation features in the `jira-wrap-sync` skill. All other skills work without it.
-
-### VS Code Configuration
-
-Add to your `.vscode/mcp.json`:
-
-```json
-{
-  "servers": {
-    "github": {
-      "command": "npx",
-      "args": ["-y", "@modelcontextprotocol/server-github"],
-      "env": {
-        "GITHUB_PERSONAL_ACCESS_TOKEN": "${input:githubPat}"
-      }
-    }
-  },
-  "inputs": [
-    {
-      "type": "promptString",
-      "id": "githubPat",
-      "description": "GitHub Personal Access Token",
-      "password": true
-    }
-  ]
-}
-```
-
-### PAT Token Requirements
-
-Create a fine-grained personal access token at [https://github.com/settings/tokens?type=beta](https://github.com/settings/tokens?type=beta) with the following scopes:
-
-- **Repository access:** Select the repos you work with
-- **Permissions:**
-  - Contents: Read and write
-  - Pull requests: Read and write
-  - Metadata: Read-only
-
-### When It's Needed
-
-Only `jira-wrap-sync` uses the GitHub MCP — specifically when creating a pull request as part of the wrap-up workflow. If you don't use that feature, you can skip this setup entirely.
-
----
-
-## Troubleshooting
-
-### MCP server not starting
-
-- Ensure `npx` is available in your PATH. Run `npx --version` in your terminal.
-- Check the VS Code Output panel (View → Output → select "MCP" from the dropdown) for error messages.
-- Try running the `npx` command manually in a terminal to see if it installs and starts correctly.
-
-### Authentication failures (401)
-
-- **Atlassian:** Verify your site URL includes `.atlassian.net` (not the full `https://` URL). Confirm your email matches your Atlassian account. Regenerate the API token if needed.
-- **GitHub:** Confirm the PAT hasn't expired. Check that it has the required scopes.
-
-### Wrong Atlassian instance
-
-- `ATLASSIAN_SITE` should be just the domain, e.g. `your-company.atlassian.net` — not a full URL like `https://your-company.atlassian.net/jira`.
-
-### Rate limiting
-
-- Atlassian APIs have rate limits. If you see 429 errors, the skills will back off automatically per the FCMP protocol. Avoid running multiple sync operations in rapid succession.
-
-### MCP calls return empty results
-
-- Confirm you have permission to access the Jira project or Confluence space you're querying.
-- Check that the project key or space key is correct.

package/toolsets/toolsets/rzlv-flow/resources/README.md

@@ -1,16 +0,0 @@
-# rzlv-flow Shared Resources
-
-Resources are shared reference material installed alongside skills. They contain protocol definitions, file structure conventions, and schema specifications that multiple skills depend on.
-
-## Installation
-
-When installed via the CLI, resources are placed in `docs/ai/resources/` in the target project. Skills reference them via relative paths and may ask the LLM to load them at the start of a workflow.
-
-## Resource Files
-
-| File | Description |
-|------|-------------|
-| `fcmp-protocol.md` | Fetch-Compare-Merge-Push sync pattern — the core protocol for safe Atlassian read/write operations |
-| `jira-file-structure.md` | Standard directory layout for local Jira mirrors (`docs/jira/{instance}/{project}/...`) |
-| `confluence-file-structure.md` | Directory layout for local Confluence page mirrors with structured and flexible modes |
-| `sync-state-format.md` | YAML frontmatter schema for Jira ticket and Confluence page files |

package/toolsets/toolsets/rzlv-flow/resources/confluence-file-structure.md

@@ -1,285 +0,0 @@
-# Confluence File Structure — Local Page Mirrors
-
-**Pattern:** Leaf Bundle local mirrors for Confluence pages
-
----
-
-## Overview
-
-Skills that interact with Confluence maintain local mirrors of pages under `docs/confluence/{instance}/{space}/`. Two modes are supported depending on how the content is created:
-
-- **Structured mode** — Orchestrator-driven, epic-based hierarchy with predefined page types
-- **Flexible mode** — User-specified location and page structure for ad-hoc documentation
-
-Both modes follow the FCMP protocol for safe sync operations and preserve manual edits made directly in Confluence.
-
----
-
-## Leaf Bundle Pattern
-
-Every Confluence page is stored as a **directory** containing an `index.md` file — never as a standalone `.md` file. This is called the Leaf Bundle pattern.
-
-### Why Folders, Not Files?
-
-- **Child pages** — A Confluence page can have child pages. The folder naturally represents this hierarchy; child pages become subdirectories.
-- **Assets** — Pages may include attachments, images, or diagrams. These are stored alongside `index.md` in the same folder.
-- **Hierarchy expansion** — New child pages can be added without restructuring. A flat file cannot grow into a parent.
-
-### DO NOT / DO
-
-```
-❌ DO NOT create flat files:
-docs/confluence/rezolve/ENG/strategic-context.md
-
-✅ DO create Leaf Bundle directories:
-docs/confluence/rezolve/ENG/strategic-context/index.md
-```
-
-This rule applies to **all** Confluence page mirrors, in both structured and flexible modes.
-
----
-
-## Base Path
-
-```
-docs/confluence/{instance}/{space}/
-```
-
-- `{instance}` — The Atlassian site identifier (e.g. `rezolve`)
-- `{space}` — The Confluence space key (e.g. `ENG`, `PROJ`)
-
----
-
-## Structured Mode
-
-Used when creating Confluence pages from Jira epic structures — typically driven by the `atlassian-orchestrator` skill.
-
-### Hierarchy
-
-```
-docs/confluence/{instance}/{space}/
-└── {initiative-name}/
-    ├── index.md                          # Initiative Overview
-    └── {epic-name}/
-        ├── overview/
-        │   └── index.md
-        ├── technical-architecture/
-        │   └── index.md
-        ├── decisions/
-        │   └── index.md
-        ├── strategic-context/
-        │   └── index.md
-        ├── research-and-findings/         # Created only if relevant content exists
-        │   └── index.md
-        ├── assumptions/                   # Created only if relevant content exists
-        │   └── index.md
-        └── implementation-guidance/
-            └── index.md
-```
-
-### Page Types
-
-| Page Type | Folder | Source | Description |
-|-----------|--------|--------|-------------|
-| Initiative Overview | `index.md` (at initiative root) | Initiative metadata | Top-level overview: goals, epic breakdown, navigation |
-| Overview | `overview/index.md` | Epic `_docs/` | High-level epic overview and goals |
-| Technical Architecture | `technical-architecture/index.md` | Epic `_docs/` | Architecture decisions and technical design |
-| Decisions | `decisions/index.md` | Epic `_docs/` | Decision log and rationale |
-| Strategic Context | `strategic-context/index.md` | Epic `_docs/` | Business context and strategic alignment |
-| Research & Findings | `research-and-findings/index.md` | Epic `_docs/` | User research, discoveries, and clarifications* |
-| Assumptions | `assumptions/index.md` | Epic `_docs/` | Assumptions with confidence levels and validation status* |
-| Implementation Guidance | `implementation-guidance/index.md` | Epic `_docs/` | High-value technical guides for development |
-
-\* Created only if the source material includes relevant content.
-
-### When to Use
-
-- Creating Confluence pages from Jira epic structure with `_docs/` content
-- Orchestrator-driven workflows that generate documentation alongside Jira structures
-
-### Sync Rules (Structured)
-
-- Generate Confluence pages from Jira `_docs/` folders
-- Sync BEFORE Jira creation (to get page IDs for linking)
-- Embed Confluence links in Jira ticket descriptions
-- Follow initiative/epic hierarchy
-
----
-
-## Flexible Mode
-
-Used for ad-hoc documentation, user-specified locations, and non-epic-based content.
-
-### Hierarchy
-
-```
-docs/confluence/{instance}/{space}/
-└── {user-specified-path}/
-    └── {page-name}/
-        └── index.md
-```
-
-No predefined structure beyond the Leaf Bundle requirement — adapts to the user's needs.
-
-### When to Use
-
-- Generic documentation and manual publishing
-- Publishing existing local docs to Confluence retroactively
-- Content created by `context-analyst` or other skills outside an epic workflow
-- Any user-driven page creation
-
-### Prompts for Flexible Mode
-
-Skills using flexible mode should ask:
-1. "Where should I place this page in Confluence? (space/parent)"
-2. "Page title?"
-3. "Should I link to a Jira ticket?"
-
-### Sync Rules (Flexible)
-
-- User specifies target location (space + parent page)
-- Optional: Link back to Jira ticket if provided
-- No predefined structure — adapt to user's needs
-- Can publish existing docs to Confluence retroactively
-
----
-
-## Ownership
-
-### Generated Pages (Structured Mode)
-
-- **Owner:** Orchestrator-type skills (e.g. `atlassian-orchestrator`)
-- **Source:** `_docs/` folders from the Jira file structure
-- **Description:** Automatically generated from epic documentation; synced to Confluence
-
-### Manual / Ad-hoc Pages (Flexible Mode)
-
-- **Owner:** User or any skill
-- **Source:** Any markdown file
-- **Location:** User-specified or derived from context
-
-### Manual Edits in Confluence
-
-- **Preserved:** Yes, always — regardless of mode
-- **Protocol:** FCMP ensures user edits in Confluence are never overwritten without merge
-
----
-
-## Sync Rules (Both Modes)
-
-- Follow the FCMP protocol when updating existing pages (see `fcmp-protocol.md`)
-- Preserve manual edits made in Confluence
-- Store page ID and URL in frontmatter after sync (see `sync-state-format.md`)
-
----
-
-## Confluence Link Format
-
-When constructing Confluence URLs:
-
-- Replace spaces in page titles with `+`
-- Use the `/wiki/display/{SPACE}/{Title}` format for display links
-- Use the `/wiki/spaces/{SPACE}/pages/{pageId}` format for direct links
-
-Example: `https://company.atlassian.net/wiki/display/ENG/Technical+Architecture`
-
----
-
-## Page File Format
-
-Each local Confluence mirror file (`index.md` inside a Leaf Bundle directory) uses YAML frontmatter for sync metadata:
-
-```yaml
----
-sync:
-  confluence_page_id: "123456789"
-  confluence_url: "https://company.atlassian.net/wiki/spaces/ENG/pages/123456789"
-  confluence_title: "Technical Architecture"
-  space: "ENG"
-  parent_page_id: "987654321"
-  last_synced: "2025-12-11T10:30:00Z"
-  version: 5
-  remote_updated: "2025-12-11T09:15:00Z"
-
-mode: "structured"  # structured | flexible
-
-source:
-  # For structured mode
-  jira_ticket: "PROJ-120"
-  doc_type: "technical-architecture"
-  generated_from: "docs/jira/rezolve/PROJ/user-authentication/_docs/technical-architecture.md"
-  bmad_docs_referenced:
-    - "docs/jira/rezolve/PROJ/PROJ-120-user-auth/_docs/technical-architecture.md"
-  jira_initiative_key: "PROJ-100"
-
-  # For flexible mode
-  # origin: "manual"
-  # linked_jira: "PROJ-123"
----
-
-# Page Title
-
-Page content in markdown, converted to Confluence storage format during sync.
-```
-
-### Frontmatter Field Reference
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `sync.confluence_page_id` | string | After first sync | Confluence page ID |
-| `sync.confluence_url` | string | After first sync | Full page URL |
-| `sync.confluence_title` | string | Yes | Exact title as it appears in Confluence (used for page lookups) |
-| `sync.space` | string | Yes | Confluence space key |
-| `sync.parent_page_id` | string | Yes | Parent page ID in Confluence |
-| `sync.last_synced` | ISO8601 | After first sync | Last sync timestamp |
-| `sync.version` | number | After first sync | Confluence page version for optimistic locking |
-| `sync.remote_updated` | ISO8601 | After first sync | Last remote change timestamp |
-| `mode` | enum | Yes | `structured` or `flexible` |
-| `source.jira_ticket` | string | Structured | Associated Jira ticket key |
-| `source.doc_type` | string | Structured | Page type (overview, technical-architecture, decisions, strategic-context) |
-| `source.generated_from` | string | Structured | Path to the `_docs/` source file |
-| `source.bmad_docs_referenced` | string[] | No | BMAD source docs used to generate the page (traceability) |
-| `source.jira_initiative_key` | string | No | Related Jira initiative key (cross-linking) |
-| `source.origin` | string | Flexible | Origin skill or `manual` |
-| `source.linked_jira` | string | Flexible | Optionally linked Jira ticket |
-
-> **Note on field naming:** The source rzlv-flow repo uses flat root-level fields (e.g. `confluence_space_key: "ENG"`). This toolset uses nested fields under `sync.*` for consistency with the Jira file schema. Both conventions represent the same data; skills should follow the nested format documented here.
-
-### Post-Sync Frontmatter Example
-
-**Before first sync (draft state):**
-```yaml
----
-sync:
-  confluence_title: "Technical Architecture"
-  space: "ENG"
-  parent_page_id: "987654321"
-mode: "structured"
-source:
-  jira_ticket: "PROJ-120"
-  doc_type: "technical-architecture"
-  generated_from: "docs/jira/rezolve/PROJ/PROJ-120-user-auth/_docs/technical-architecture.md"
----
-```
-
-**After first sync (populated by sync operation):**
-```yaml
----
-sync:
-  confluence_page_id: "123456789"
-  confluence_url: "https://company.atlassian.net/wiki/spaces/ENG/pages/123456789"
-  confluence_title: "Technical Architecture"
-  space: "ENG"
-  parent_page_id: "987654321"
-  last_synced: "2025-12-11T10:30:00Z"
-  version: 1
-  remote_updated: "2025-12-11T10:30:00Z"
-mode: "structured"
-source:
-  jira_ticket: "PROJ-120"
-  doc_type: "technical-architecture"
-  generated_from: "docs/jira/rezolve/PROJ/PROJ-120-user-auth/_docs/technical-architecture.md"
----
-```
-
-See `sync-state-format.md` for the full frontmatter schema and worked examples.

package/toolsets/toolsets/rzlv-flow/resources/confluence-page-templates/README.md

@@ -1,19 +0,0 @@
-# Confluence Page Templates
-
-Starter scaffolds for Confluence pages created by the `atlassian-orchestrator` skill (structured mode). Each template contains standard section headings and placeholder tokens.
-
-## Usage
-
-- Templates provide consistent section headings across generated pages.
-- Replace `{tokens}` with actual content during page creation.
-- Skills can load these templates instead of generating page structure from scratch.
-- Users can customize templates to match their team's conventions.
-
-## Templates
-
-| Template | File | Description |
-|----------|------|-------------|
-| Initiative Overview | `initiative-overview.md` | Top-level initiative page: goals, epic breakdown, navigation |
-| Strategic Context | `strategic-context.md` | Business goals, product vision, strategic decisions |
-| Technical Architecture | `technical-architecture.md` | System design, tech decisions, implementation patterns |
-| Decisions | `decisions.md` | Consolidated decision log with rationale |

package/toolsets/toolsets/rzlv-flow/resources/confluence-page-templates/decisions.md

@@ -1,36 +0,0 @@
----
-sync:
-  confluence_page_id: ""
-  confluence_url: ""
-  confluence_title: "Decision Log — {Initiative/Epic Name}"
-  space: "{SPACE}"
-  parent_page_id: ""
-  last_synced: ""
-  version: 1
-  remote_updated: ""
-mode: "structured"
-source:
-  jira_ticket: "{EPIC-KEY}"
-  doc_type: "decisions"
-  generated_from: ""
----
-
-# Decision Log — {Initiative/Epic Name}
-
-## Active Decisions
-
-| ID | Decision | Date | Rationale | Confidence | Impact |
-|----|----------|------|-----------|------------|--------|
-| {id} | {decision} | {date} | {rationale} | {High/Medium/Low} | {impact area} |
-
-## Pending Decisions
-
-| ID | Question | Context | Options | Owner | Deadline |
-|----|----------|---------|---------|-------|----------|
-| {id} | {question} | {context} | {options} | {owner} | {deadline} |
-
-## Superseded Decisions
-
-| ID | Original Decision | Superseded By | Date | Reason |
-|----|-------------------|---------------|------|--------|
-| {id} | {original} | {new decision} | {date} | {reason} |

package/toolsets/toolsets/rzlv-flow/resources/confluence-page-templates/initiative-overview.md

@@ -1,40 +0,0 @@
----
-sync:
-  confluence_page_id: ""
-  confluence_url: ""
-  confluence_title: "{Initiative Name}"
-  space: "{SPACE}"
-  parent_page_id: ""
-  last_synced: ""
-  version: 1
-  remote_updated: ""
-mode: "structured"
-source:
-  jira_initiative_key: "{INITIATIVE-KEY}"
----
-
-# {Initiative Name}
-
-## Overview
-
-{Brief summary of the initiative — 2-3 sentences covering purpose and strategic goals.}
-
-## Epic Breakdown
-
-| Epic | Description | Status | Stories | Confluence |
-|------|-------------|--------|---------|------------|
-| {EPIC-KEY} | {Epic summary} | {status} | {count} | [link]({confluence_url}) |
-
-## Quick Navigation
-
-- [{Epic Name} — Overview]({epic-overview-url})
-- [{Epic Name} — Technical Architecture]({epic-tech-arch-url})
-- [{Epic Name} — Decisions]({epic-decisions-url})
-
-## Timeline & Dependencies
-
-{Key dates, milestones, and cross-team dependencies.}
-
-## Success Criteria
-
-{Measurable outcomes that define initiative success.}