From csdlc
The CSDLC methodology reference — pipeline steps, roles, refinement practices, rituals, context management. Use whenever you need to understand how CSDLC works, when a user asks about the process, when you're deciding which pipeline step applies, or when crafting agent prompts. Also triggers when terms like "refinement", "design doc", "Step 0", "Lightning Strike", "managed agent", "Hurricane Pattern" come up without clear context.
npx claudepluginhub danhannah94/claymore-plugins --plugin csdlcThis skill uses the workspace's default tool permissions.
This skill provides the full Claymore Software Development Lifecycle methodology.
Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.
Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.
Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.
This skill provides the full Claymore Software Development Lifecycle methodology.
Read PROCESS.md (sibling file) for the complete reference. Below is a quick
orientation so you know what's in there and when to consult which section.
Pipeline: Refinement (continuous) → Step 0 (Design Doc) → Step 1 (Story Breakdown) → Step 2 (Agent Prompt Crafting) → Step 3 (Execution) → Step 4 (AI Lead Review) → Step 5 (QA) → Step 6 (Human Review → Ship)
Roles: Human = Technical Product Owner + QA Director. AI Lead = Architect + Scrum Master + Tech Lead. Sub-agents = disposable dev team.
Entry points: New project/epic → Step 0. Bug fix / small task → Step 1.
Core principle: Refinement is the practice, not a step. Resolve ambiguity before code. 30 minutes of Step 0 saves hours of rework.