Menu
Skills in this repository
SkillsMP has collected 130 skills from DauQuangThanh/kiss-u. Open a skill to review its source and details.
DauQuangThanh/kiss-uShowing 40 of 130 collected skills.
Maintains the product backlog — an ordered markdown list of user stories / items keyed by priority, with lightweight estimates, acceptance-criteria pointers, and status. Drafts and re-orders the list from priorities the user states; does not decide priority…
Authors a structured bug report file per bug at docs/bugs/BUG-NNN-<slug>.md. Captures repro, expected vs actual, severity, affected version, and traceability to the failed test case or user story. Use when filing a new bug, documenting a defect found during…
Triages open bugs into fix-now / next-sprint / defer / won't-fix buckets from severity + priority + age + business cost. Produces a dated triage list the bug-fixer / PO can act on. Use when prioritising a bug backlog, deciding what to fix next, or preparing…
Authors C4 model diagrams (Context / Container / Component) as Mermaid flowcharts. Produces three files per project so the system can be described at every zoom level. Draws what the user has declared; does not invent components. Use when creating…
Maintains a project change-request ledger. Captures incoming change requests, drafts impact assessments (scope / schedule / budget / quality), records CCB decisions the user reports, and tracks implementation. Authors and maintains the ledger; never approves,…
Maintains the change register — one row per applied bug-fix — with bug id, commit/PR, files touched, regression test, and the reviewer. Records what actually shipped; does not ship anything. Use when recording a bug fix that has shipped, updating the change…
Drafts CI/CD pipeline design for the project — stages, triggers, quality-gate integration, artefact flow. Produces a provider- neutral pipeline doc + a provider-specific YAML skeleton. Does not provision CI; does not run pipelines. Use when designing a CI/CD…
Identifies underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec. Use when a spec has gaps or ambiguities, before implementation starts, or when the team disagrees on…
Scans an existing codebase and produces an overview: language + LOC by directory, detected frameworks, entry points, test coverage signals, build/lint/format tooling. Serves as input for all other technical-analyst skills. Use when onboarding to a new…
Drafts Dockerfile / compose / image-build strategy for the project. Produces a multi-stage Dockerfile starter, a compose file for local dev, and the design doc. Does not build or push images. Use when dockerising an application, planning a container strategy,…
Audits third-party dependencies: lists direct + transitive deps, cross-references against CVE databases (via WebSearch/WebFetch), surfaces licence conflicts and abandonware. Records audit as a dated file so subsequent runs show drift. Use when checking for…
Renders the project's internal module-dependency graph + external dependency list as a Mermaid diagram. Works from imports + the lockfile produced by kiss-codebase-scan. Use when visualising module dependencies, understanding code structure, or identifying…
Drafts the deployment strategy + release runbook — canary / blue-green / rolling, promotion flow, rollback, feature flags, release-notes seed. Produces a runbook the on-call team uses. Does not deploy. Use when planning a deployment strategy, defining a…
Drafts detailed module / API / data-model / integration design for the active feature, under docs/design/<feature>/. Uses the architecture intake + ADRs + spec as inputs. Does not commit to implementation timelines. Use when designing technical…
Generates a custom checklist for the current feature based on user requirements, validating quality and completeness of requirements in a given domain. Use when reviewing feature completeness, running pre-implementation checks, or verifying that requirements…
Auto-commit changes after a kiss command completes
Create a feature branch with sequential or timestamp numbering
Initialize a Git repository with an initial commit
Validate current branch follows feature branch naming conventions
Executes the implementation plan by processing and executing all tasks defined in tasks.md. Use when coding a feature from an existing tasks.md, executing implementation tasks one by one, or when the plan and design are ready and it is time to build.
Drafts infrastructure-as-code plan — cloud accounts, networks, compute/storage/database resources, IAM boundaries. Produces a tool-neutral design + a starter module for the chosen IaC tool. Does not provision anything. Use when planning cloud infrastructure,…
Drafts the observability plan — logs, metrics, traces, SLIs/SLOs, alerts, dashboards. Produces a design doc + starter dashboard/alert YAML. Does not provision monitoring. Use when setting up monitoring for a project, defining SLOs/SLIs, or planning alerting…
Executes the implementation planning workflow using the plan template to generate design artefacts. Use when creating an implementation plan for a feature, breaking down architecture into actionable design documents, or before running kiss-taskify.
Drafts and maintains a project plan: scope statement, work breakdown structure (WBS), milestones, dependencies, critical path, resource allocation, and Definition of Done. Supports Agile/Scrum, Kanban, Waterfall, and Hybrid methodologies. Also drafts the…
Defines quality gates (coverage thresholds, lint / type / security scan pass criteria, performance budgets) that every PR and every release must pass. Produces a gate definition the CI pipeline enforces. Does not enforce them itself. Use when defining quality…
Reviews a feature's code for maintainability, SOLID/DRY/KISS compliance, cyclomatic complexity, and adherence to project standards. Produces a feature-scoped review file with findings, severity, and recommended fixes. Does not modify code. Use when reviewing…
Authors a regression test per fixed bug so the same defect cannot ship again without being caught. Writes test files into the project's own test tree + a per-bug index entry at docs/testing/regression-index.md. Use when a bug has been fixed and needs a…
Synthesises provided retrospective notes (or a pasted What-went-well / What-didn't / Try-next transcript) into structured action items with owners and target sprints. Does NOT facilitate the retro — the team holds it and provides the notes. Use when…
Maintains a project risk register. Identifies risks, scores likelihood × impact, assigns categories and owners, drafts mitigation and contingency plans. Drafts and maintains the register; humans own the decisions to accept, mitigate, transfer, or avoid each…
Drafts a product roadmap grouping backlog items into release windows (Now / Next / Later or date-based). Proposes windows from the backlog's priority order; the user (product-owner) confirms. Does not commit a team to a delivery date. Use when planning…
Reviews a feature's code + config against OWASP Top 10:2025 and common CWE patterns. Produces a per-feature security review with findings, severity, and remediation outlines. Does not deploy, write exploits, or modify code. Use when reviewing security…
Creates or updates the feature specification from a natural language feature description. Use when starting work on a new feature, creating a spec from a user story or idea, or when the feature description needs to be formalised into a structured…
Drafts a sprint plan — sprint goal, candidate backlog items, capacity arithmetic, and risk flags — from the backlog + a user-provided velocity. Prepares the artefact; the team owns the commitment. Does not facilitate a planning meeting. Use when planning a…
Logs daily standup notes from content the user pastes in. Extracts blockers into a tracked impediments list. Does NOT facilitate the standup — the team runs the meeting and tells the AI what happened. Use when recording daily standup notes, tracking…
Drafts a project status report (RAG status, accomplishments, next steps, budget variance, open blockers, and escalated risks) from facts the user supplies and upstream artefacts. Produces a dated report file the user can share with stakeholders; does not send…
Generates an actionable, dependency-ordered tasks.md for the feature based on available design artefacts. Use when breaking down a feature into implementation tasks, creating tasks.md from a plan or design doc, or before running kiss-implement.
Converts existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artefacts. Use when creating GitHub issues from tasks.md, exporting tasks to a GitHub project board, or when the team tracks work in GitHub…
Researches technology options for a named decision area (frontend framework, database, messaging, identity, etc.) using WebSearch / WebFetch when available. Produces a pros/cons table + typical cost signal per candidate. Records sources. Does not pick the…
Generates feature-level test cases from user stories and acceptance criteria. Produces a dependency-ordered test-case file the tester walks through during execution. Use when writing test cases, generating a test plan from acceptance criteria, or before…
Maintains a test-execution ledger for the active feature. Records pass / fail / skipped counts per run, links failed cases to bug reports, and summarises coverage against acceptance criteria. The AI records; the tester runs the tests. Use when logging test…