Jo-bity
- 8 skills
- 0 followers
- 3 hours ago last updated
- ▌ Adr Log · jo-bity bundleInterview the user about the newest decisions on a capability and persist each qualifying decision as a decision record (ADR file) in the Obsidian vault ($OBSIDIAN_VAULT) under 02_Entwicklung/<Capability>/ADR/, linked to the capability's Arbeitsdokument. Decision records are append-only — amendments are appended, original rationale is never rewritten. Use when the user wants to record recent decisions as decision records, after a grilling session produced decisions worth persisting, or when converting documented decisions from a working note into decision record files.
- ▌ Doc Drift · jo-bityCheck a capability's documentation against the current codebase and report every statement that no longer holds — stale claims, decisions silently reverted in code, and documented behaviour that was never built. Reports and routes findings; never edits the notes itself. Use when the user asks whether a capability note or ADR is still accurate, wants to audit documentation against code, or suspects a note has gone stale.
- ▌ Jira Ticket · jo-bity bundleWrite or update Jira tickets (Initiative, Epic, Capability, Story, Task, Bug, Spike) in a consistent German section structure with correct Markdown for a Jira MCP server. Use when the user wants to create, write, refine, or restructure an Initiative/Epic/Capability/Story/Task/Bug/Spike, or fix Jira ticket formatting.
- ▌ Decision Doc · jo-bityDistill a working note in the Obsidian vault ($OBSIDIAN_VAULT) into a condensed, standalone "Entscheidungen & Anforderungen" summary document with executive summary, newest-first decision register, glossary, and open points. Use when user asks for a decisions and requirements summary ("Entscheidungen & Anforderungen"), wants to condense a feature working note into a decision document, or references an existing "… — Entscheidungen & Anforderungen.md" as template.
- ▌ Obsidian Note · jo-bity bundleWrite a document or work note into the Obsidian vault ($OBSIDIAN_VAULT) — either a polished standalone document grounded in codebase research, or a dated progress/work note (newest entry first). Use when the user wants to produce technical documentation, an architecture analysis or investigation report, OR to write up what was done, log findings, record decisions, or document the outcome of an investigation/implementation.
- ▌ Capability Doc · jo-bity bundleInterview the user about how the newest decisions (ADRs) change the current functionality and architecture of a capability, then rework the capability's living note in the Obsidian vault ($OBSIDIAN_VAULT) by replacing outdated statements in place — current-state only, no ADR prose, split into fachliche and technische Anforderungen. Use when the user wants to update a capability note (like KYC or Onboarding API) after new decisions, or to convert a dated append-only working note into a living capability doc.
- ▌ Capability Scan · jo-bityBootstrap a capability's documentation folder from the codebase — research the services that implement it with parallel Explore agents, write the first Arbeitsdokument describing the current state, and propose ADR candidates for decisions visible in the code. Use when a capability exists in code but has no note yet, when starting documentation for an undocumented service or bounded context, or when the user asks to document an existing system from scratch.
- ▌ Requirements Snapshot · jo-bityCreate a dated, standalone "Entscheidungen & Anforderungen" snapshot for a capability from its living capability note and its ADR folder in the Obsidian vault ($OBSIDIAN_VAULT) — executive summary, decision register resolved from the ADR files (newest first), requirements, open points. Use when the user asks for a requirements snapshot or "Entscheidungen & Anforderungen" for a capability managed with adr-log + capability-doc; for legacy working notes without an ADR folder, the older decision-doc skill applies instead.