SpillwaveSolutions avatar

worklog

v0.24.13

by SpillwaveSolutions · author: Rick Hightower

worklog is an Agent Plugin published by SpillwaveSolutions. It packages 13 skills. We fetched the plugin.json from GitHub on 2026-11-13 and checked it against the official Agent Plugins 1.0.0 schema.

WikiTicket SDD (worklog): git-native plans, tickets, roadmaps, and wiki publishing. Multi-host bindings. Knowledge-tree writes live in okf-plugin.

Package we checked

The manifest we fetched is plugin/plugin.json in SpillwaveSolutions/wiki_ticket_sdd. The plugin root is the directory that holds that file. Its $schema is https://agent-plugins.org/schemas/1.0.0/plugin.schema.json. The manifest lists 13 skills and no MCP servers.

Skills
13
MCP servers
0
Stars
11
License
MIT
Repo created
2026-07-18
Last pushed
2026-11-10
Publisher type
Organization
Version
0.24.13

Links

Skills · 13

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, archite…
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 ti…
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/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 tic…
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

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

Category

Productivity & Workflow. Assigned by this directory. Agent Plugins 1.0.0 has no category field, so no manifest declares one.

Keywords

worklog · isolation · agent-plugins · claude-code · grok-build · codex · deep-agents · grok-bot

Related by publisher and keywords

  • okf-agent-graphSpillwaveSolutions

    OKF Agent Graph Engineering Runtime (AGER): author multi-agent loop graphs as OKF and reverse-engineer existing agent stacks. Multi-host bindings and write isolation.

  • Data Engineering Knowledge Capture: schemas, lineage, medallion, semantic models, and glossary into a durable OKF knowledge graph. Multi-host bindings and write isolation.

  • second-brain-coreSpillwaveSolutions

    Shared foundation for Spillwave ContentPack plugins: OKF schemas, typed edges, deterministic write helpers, progressive-disclosure packing, and write isolation.

  • okf-graph-engSpillwaveSolutions

    OKF graph engine: validate, walk, pack, and impact-analyze Git-native knowledge graphs. Owns Catalog and ContextPack. Domain nouns live in PKC, SAC, DEKC, and AGER.

  • project-knowledge-captureSpillwaveSolutions

    Project Knowledge Capture: meetings, experiments, decisions, TicketLink/WikiTicket work, and project-memory nouns into a durable OKF knowledge graph. Multi-host bindings and write isolation for shared second brains.

  • system-architecture-captureSpillwaveSolutions

    System Architecture Capture: reverse-engineer services, packages, IaC, CI/CD, IAM, and runtime topology into a durable OKF knowledge graph. Multi-host bindings and write isolation for shared second brains.

Add the verified badge to your README[![Verified by AgentPluginsDirectory.com against Schema 1.0.0](https://agentpluginsdirectory.com/badge.svg)](https://agentpluginsdirectory.com/plugins/worklog--spillwavesolutions)

✓ Verified . We fetched the manifest from GitHub and checked it against the official Agent Plugins 1.0.0 schema at agent-plugins.org.