cmk:feature-spec
No SKILL.md available for this skill.
View on GitHubMore from commandosslabs/ai-devkit
cmk:prd
Create or iterate product requirements documents. Use whenever someone wants to draft, refine, or update a PRD — whether from conversation notes, research sessions, user feedback, Notion docs, or direct instructions. Also triggers when users discuss product scope, success criteria, user needs, or say things like "save this as requirements" or "let's define what we're building".
12cmk:docs
Bootstrap or update the /docs directory structure with navigation files, guides, and templates. Use when someone wants to set up docs for a new repo, check if their docs structure is current, or sync scaffolding after devkit updates. Also triggers when users mention "docs structure", "initialize docs", or "docs scaffold".
12cmk:adr
Create or update architecture decision records for system-level technical choices. Use whenever someone needs to record, revise, or document a technical decision with trade-offs — like choosing a database, communication protocol, or infrastructure pattern. Also triggers for "record this decision", "we decided to use X over Y", or "document why we chose this approach".
12cmk:system-design
Create or iterate system design documents covering architecture, tech stack, components, and cross-cutting concerns. Use whenever someone wants to draft, refine, or update a system design — whether discussing architecture decisions, tech stack changes, infrastructure layout, or scaling strategy. Also triggers for "how should we build this", "design the backend", or "update the architecture".
12cmk:rule
Codify engineering standards into docs/rules/. Use whenever someone wants to create, update, or promote knowledge into enforceable coding rules and conventions that agents follow during development. Also triggers for "add a rule that...", "make this a standard", "promote this learning to a rule", "update our coding conventions", or "what are our engineering rules".
8cmk:learn
Extract and record non-obvious learnings, gotchas, and valuable knowledge from any input — conversations, research sessions, debugging, files, or user instructions. Use whenever someone wants to capture what they learned, save a gotcha, or preserve insights for future reference. Also triggers for "remember this", "save this learning", "that was a long session — capture the key findings", or "what do we know about X".
8