Loading...
Loading...
Found 33 Skills
Complete workflow for developing new features from design to deployment. Use when starting a new feature, adding functionality, or building something new.
Coordinate parallel feature development with file ownership strategies, conflict avoidance rules, and integration patterns for multi-agent implementation. Use this skill when decomposing features for parallel development, establishing file ownership boundaries, or managing integration between parallel work streams.
Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.
Use when the user wants a full feature-development chain: clarify a rough feature idea into a prompt, review it with the user, then hand it to grill-with-docs, to-prd, to-issues, and tdd.
Use when the user wants to turn a feature idea, change request, or rough requirement into a precise feature-development prompt for one or more codebase projects.
Use when creating or developing Laravel features, before writing code or implementation plans - refines rough ideas into fully-formed Laravel designs through collaborative questioning, alternative exploration, and incremental validation.
Guided feature development with codebase understanding and architecture focus. Use for implementing features systematically: explore → clarify → design → implement → test → review.
Ultra-lightweight channel for feature workflows: No need to write design docs, checklists, or conduct phased reviews. Let AI write code directly as it normally would, but before it starts, tell it where the CodeStable knowledge base in the project is and how to search it. This way, the code it writes will have fewer pitfalls and be more consistent with project conventions. Trigger scenarios: Users say "fast mode", "fastforward", "skip all those steps", "just start coding", "help me make xxx" and the requirement is too small to go through the design process.
When developing new features, follow this sub-process — take the vague idea of "add X capability" through to the acceptance closure, with solution documents archived so that both AI and users can later check the original thinking and decision rationale. Trigger scenarios are focused on adding new capabilities ("develop new feature", "add X", "implement XX"), and do not handle bugs in existing code. This skill only acts as a router, deciding which sub-skill to trigger next among brainstorm / design / fastforward / implement / acceptance based on existing artifacts.
Use when the user is starting a new project or feature, or mentions "concept", "roadmap", "feature", "spec", "plan", "idea", or "what to build". Walks them through three plain-English phases — Concept (what & why) → Roadmap (the path) → Features (the work) — producing one-page markdown artifacts under `specdriven/` that anchor every later turn. Skip when the task is already small and well-scoped (a rename, a one-line bug fix).
This skill should be used for structured feature development with codebase understanding. Triggers on /do command. Provides a 5-phase workflow (Understand, Clarify, Design, Implement, Complete) using codeagent-wrapper to orchestrate code-explorer, code-architect, code-reviewer, and develop agents in parallel.
Implement an existing PRD (`Type: feat`/`fix`/`chore`), update tests/checks, and mark completed PRD checklist items. Triggers: implement prd, build feature from prd, execute prd checklist.