krammeagents-md
This skill should be used when the user asks to "update AGENTS.md", "add to AGENTS.md", "maintain agent docs", or needs to add guidelines to agent instructions. Guides discovery of local skills and enforces structured, keyword-based documentation style.
SKILL.md
| Name | krammeagents-md |
| Description | This skill should be used when the user asks to "update AGENTS.md", "add to AGENTS.md", "maintain agent docs", or needs to add guidelines to agent instructions. Guides discovery of local skills and enforces structured, keyword-based documentation style. |
kramme-cc-workflow
This repository contains Claude Code workflow plugins and support scripts.
<!-- prettier-ignore-start --><!-- prettier-ignore-end -->[!IMPORTANT] Several skills in
kramme-cc-workfloware adapted from Addy Osmani's agent-skills. See the detailed attribution list inkramme-cc-workflow/README.md.
Main Plugin Contents (kramme-cc-workflow)
88skills inskills/(SIW, PR workflows, Linear workflows, verification, documentation utilities, and session helpers)21specialized agents inagents/for review and analysis- built-in hooks in
hooks/hooks.jsonfor command safety, non-interactive git enforcement, formatting, and context links - release and install tooling in
scripts/ - Bats test suite in
tests/
Detailed documentation is available in kramme-cc-workflow/README.md.
Local Repository Maintenance
This workspace also includes local maintenance skills under .agents/skills/, exposed to Claude Code through the .claude/skills symlink. These are for maintaining this repository and are not shipped as part of the public plugins.
| Skill | Description |
|---|---|
/kramme:skill:audit-sources | Audits one or more skills against declared inspiration sources, bootstraps missing references/sources.yaml manifests, compares fetched source snapshots, and writes .context/skill-source-audit-<timestamp>.md reports. |
What SIW Is
SIW means Structured Implementation Workflow.
It is a local, file-based workflow for planning and implementing non-trivial work in a repository. Instead of relying on an external tracker, SIW keeps specification, issue breakdown, and progress state in versioned Markdown files.
SIW typically manages:
- specification files (created or linked during setup)
siw/LOG.mdfor decisions and progress notessiw/OPEN_ISSUES_OVERVIEW.mdas the active issue indexsiw/issues/for issue files with status and implementation context
Common SIW command flow:
/kramme:siw:init # create or link spec + initialize siw/
/kramme:siw:generate-phases # break spec into phase-based issues
/kramme:siw:issue-implement # implement one issue
/kramme:siw:implementation-audit
/kramme:siw:issue-reindex
Related SIW commands include /kramme:siw:issue-define, /kramme:siw:spec-audit, /kramme:siw:breakdown-findings, /kramme:siw:reset, /kramme:siw:reverse-engineer-spec, and /kramme:siw:remove.
Installation
Marketplace:
claude /plugin marketplace add Abildtoft/kramme-cc-workflow
claude /plugin install kramme-cc-workflow@kramme-cc-workflow
Local install:
claude /plugin install /path/to/kramme-cc-workflow/kramme-cc-workflow
Update marketplace install:
claude /plugin marketplace update kramme-cc-workflow
Example Commands
After installation, common entry points are:
/kramme:siw:init
/kramme:pr:code-review
/kramme:pr:fix-ci
/kramme:verify:run
Repository Structure
| Directory | Purpose |
|---|---|
.agents/skills/ | Local repository-maintenance skills used while developing this repo |
.claude/skills | Symlink exposing local maintenance skills to Claude Code |
kramme-cc-workflow/ | Main plugin: workflow automation, review agents, hooks, and verification |
Documentation
License
MIT