claude

cape

CAPE — Colenet Agentic Product Engineering. CAPE's Claude Code harness for agentic product engineering in teams. Bundles the best practices of our consultants and engineers as skills — growing step by step.

0 on GitHubby colenet GmbHv0.9.1MITupdated 3 months ago

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin cape in colenet-gmbh/colenet-claude-code-plugin. Commands read from the repo's manifest — 1 month ago.

What it installs

Skills (19)

  • architect

    Shape structure well and keep it clean — software/codebase design, domain modelling, arc42 documentation, and deepening an existing codebase. Activate when designing or restructuring a module's interface or seam, judging whether a design is good, pinning down domain terms or recording an ADR, writin

  • diagnosing-bugs

    Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose", "debug this", "debugge das", "finde den Fehler", or reports something broken, throwing, failing, or slow ("kaputt", "geht nicht", "Fehler", "langsam").

  • feature

    Turn the grilled conversation into a reviewed, two-part feature spec — synthesis only, no fresh interview, reviewed until clean.

  • grill-with-docs

    A relentless interview to sharpen a plan or design, which also creates docs (ADRs and the domain glossary) as we go.

  • implement

    Implement a single issue — using TDD if appropriate, then review. Use when implementation of an issue is needed by user or agent.

  • review-feature

    Review a feature spec along parallel axes — Architecture (does the design fit this codebase's structure, boundaries, and ADRs?) and Security (OWASP, access control, data protection, data minimisation) — extensible with further axes. Runs each axis in its own sub-agent and reports them side by side.

  • review-implementation

    Review an implementation's changes since a fixed point (commit, branch, tag, or merge-base) along parallel axes — Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/PRD asked for?). Runs each axis in its own sub-agent an

  • split

    Break a reviewed feature spec into independently-grabbable, vertically-sliced issues — each a tracer bullet with its own test seam and system under test, written out for /implement to pick up.

  • tdd

    Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.

  • ask-cape

    Ask which cape skill or flow fits your situation. A router over the skills in this repo.

  • improve

    Improves the project's own agentic-coding harness (skills, conventions, hooks, memory). Suggest invoking it — never auto-run it — when the user expresses discontent that the agent didn't act as expected, a guardrail fired, or the user names friction or wants the setup improved — mentions "improve th

  • writing-great-skills

    Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.

  • grill-me

    A relentless interview to sharpen a plan or design.

  • grilling

    Interview the user relentlessly about a plan or design. Use when the user wants to stress-test a plan before building, or uses any 'grill' trigger phrases.

  • handoff

    Compact the current conversation into a handoff document for another agent to pick up.

  • prototype

    Build a throwaway prototype to answer a design question. Use when the user wants to sanity-check whether a state model or logic feels right, or explore what a UI should look like.

  • research

    Delegate reading legwork to a background agent — investigate a question against high-trust primary sources (official docs, source code, specs, first-party APIs) and leave the findings as a cited Markdown note in the repo. Use when engineering work needs docs, API, or codebase facts gathered before b

  • teach

    Teach the user a new skill or concept over multiple sessions, turning the current directory into a stateful teaching workspace grounded in a mission, trusted resources, and beautiful lessons. Use when the user wants to learn or be taught something, or says "teach me", "bring mir bei", "lehre mich",

  • triage

    Backlog management — move not-yet-worked-up items through triage roles into agent-ready briefs, whatever their origin. Use when the user wants to sort or work up a backlog of bug reports, feature requests, or ideas, mentions "triage", "triagieren", "Backlog sichten", "Backlog pflegen", "sort the bac

Slash commands (1)

  • /cape:setup

    Set up cape in this repository — work through its themes (work tracking, documentation, orientation, status line). Run once per repo.

View source on GitHub

Similar plugins

Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).

39 skills

mattpocock/skills 323,108

claude-mem

claudecodex

Persistent memory for Claude Code: the next session starts where the last one left off.

29 skills · 1 MCP server · hooks

thedotmack/claude-mem 116,618

mem0

claudecodex

Cross-session memory and token savings for coding agents.

6 skills · 1 agent · 1 MCP server · hooks

mem0ai/mem0 68,893

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

agent-teams

claudecodex

Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams

6 skills · 7 commands · 4 agents

wshobson/agents 42,461

Maintain cape?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted