Ambiguous specifications create implementation gaps, security risks, and costly rework. This skill reviews plans through architecture, security, quality, user, and governance perspectives before engineers begin implementation.

Complex features fail when requirements, architecture effects, and verification criteria remain unclear. This skill guides agents through research and produces an implementation-ready Gjalla specification.

Vague product ideas cause unclear scope, weak acceptance criteria, and delivery risk. This skill turns stakeholder input into a structured, measurable Product Requirements Document.

Software documentation often mixes learning, task, reference, and conceptual content. This skill separates those needs and produces focused Markdown for a defined audience.

Creating Enact tools requires clear structure, schemas, commands, and publishing steps. This skill gives Claude, Codex, and Claude Code a compact reference for Enact authoring.

Teams need clear specifications before implementation starts. This skill turns feature requirements into PRD, technical, and UX specs with validation steps.

Troubleshooting sessions can leave important details scattered across notes and chat history. This skill helps Claude, Codex, or Claude Code create a clear issue report.

Teams often let AI project instructions grow into one hard-to-maintain file. This skill helps create focused Claude Code rule files with scoped paths, clear names, and update steps.

MCP servers need the right transport for local, web, and cloud deployments. This skill compares stdio, SSE, HTTP streaming, and custom options.

MCP server authors need repeatable patterns for exposing files, records, and API data as resources. This skill guides URI design, listing, fetching, MIME handling, caching, streaming, and testing for Claude, Codex, and Claude Code.

Large Markdown projects become hard to navigate when headings change. This skill helps generate, preview, and update tables of contents across files.

Feature work can drift when requirements are missing or stale. This skill defines requirement files, versioning, issue links, and backup steps.

Teams lose time when requirements are vague or forced into one template. This skill guides Claude, Codex, and Claude Code to create clear, testable requirements for each domain.

Teams need changelogs that reflect code, requirements, and design changes. This skill guides Claude, Codex, and Claude Code through git-based changelog updates.

AI governance records are hard to create from code, interviews, and operational context. This skill guides capture, validation, review, and confirmed KI-Register submission.

Teams need repeatable ways to package workflows and domain knowledge for AI agents. This skill guides Claude Code through designing, writing, and testing focused Agent Skills.

Process skills often fail when agents face time pressure, authority pressure, or sunk cost. This skill gives a repeatable subagent test workflow to expose failures and improve instructions.

Reusable skills often stay local because contributors lack a clear publishing workflow. This skill gives Claude, Codex, and Claude Code a structured process for preparing a branch, commit, push, and pull request.

Project work often spreads across chats, tasks, and pull requests. Workhub keeps issues, PR records, decisions, and status in one docs folder.

Software projects often fail when requirements, design choices, and tasks are unclear. This skill turns project ideas into structured planning documents for Claude, Codex, and Claude Code workflows.