WikiTicket SDD

Plugin worklog from marketplace spillwave-second-brain in SpillwaveSolutions/second-brain-marketplace. Commands read from the repo's manifest — 2 days ago.

Skills (16)

• classify

  Propose work items from recent conversation (flag-gated classifier). Use when the Stop hook requests classification or when asked to sweep a conversation for untracked work. Propose-only: writes .work/suggestions.jsonl, never the event log.

• design-docs

  Generate or sync the design document or code walkthrough. Live current pair regenerated from the actual code; a release freeze is a short tag+hash+delta note, not a full dated copy. Uses document-specialist v3.2.2, design-doc-mermaid v1.1.1, plantuml v1.2.2. Use when asked for a design doc, architec

• integration-guide

  Look up how wiki_ticket_sdd integrates with a specific SDD tool or ticket/wiki system — Superpowers, GSD, SpecKit, OpenSpec, Jira, Confluence, GitHub, GitLab, Azure DevOps (ADO), AWS CodeCatalyst, or Google Cloud DevOps (GCP). Use when asked how to set up, configure, or use one of these, or when tic

• issue-description

  Write rich, durable issue/ticket descriptions. Use when creating or updating tickets by hand, when composing bodies for ticket-sync, or when a work item needs a description a future reader (human or agent) can act on without archaeology.

• merge-green

  Merge PRs only when all quality gates pass. Use whenever asked to merge a PR, complete a merge, or land a branch — arms GitHub auto-merge and falls back to polling instead of merging blind or bypassing.

• plan-capture

  Capture an approved plan as tracked work items. Use when exiting plan mode, when the user approves a plan, or says "capture this plan". Writes docs/plans/<date>-<slug>.md and appends the plan''s tasks to .work/todo.jsonl via bin/wiki-ticket/worklog.

• plan-next

  Decide what to work on next — use when asked "what should we do next", "what's most important", or when planning a new work session.

• pr-description

  Write a high-context PR description for any substantial PR. Use whenever creating or editing a pull request body — the description must let a reader with zero prior context understand what is being built, why, where it sits in the larger system, and exactly what changed, without digging through tick

• release

  Cut a versioned release — stamp the changelog, snapshot the roadmap, tag, create the platform release, publish, and sync. Use when asked to "cut a release", "ship vX.Y.Z", "tag a version", or when an unreleased changelog section is ready to go out.

• status-report

  Generate a status report. Use when asked for a status report, a standup summary, "what changed this week", or "what did we ship". Writes docs/status/<date>-<kind>.md, commits, and publishes — never paste an unrecorded status into chat.

• ticket-sync

  Push work items to the team's configured ticketing system (GitHub Issues, Jira, Azure DevOps, GitLab, Linear...). Use when asked to sync tickets, after closing out a plan, or when items should be visible in the tracker. Push and pull.

• wiki-publish

  Publish docs (roadmap, plans, user guide, status) to the team's configured wiki. Use when asked to publish/sync docs to the wiki, after cutting a roadmap snapshot, or when a plan/status report should be visible outside the repo.

• work-track

  Track work items — use when creating, updating, closing, or listing work items, or when discovering unplanned work mid-flight ("we also need to…", a bug found while doing something else).

• cursor-worklog

  Bind a Cursor agent (including Grok Bot cloud sessions) to the worklog ContentPack.

• worklog-deep-agents

  Bind WikiTicket SDD for LangChain Deep Agents / Deep Agents Code.

• grok-bot-wiki-ticket-sdd

  Bind a Grok Bot agent to WikiTicket SDD. Worklog appends; knowledge-tree writes live in okf-plugin.

Similar plugins