dauquangthanh
- 133 skills
- 0 followers
- last month last updated
- ▌ Kiss Retrospective · dauquangthanh bundleSynthesises 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 processing sprint retrospective notes, capturing action items from a retrospective, or converting retro output into a tracked list.
- ▌ Kiss Risk Register · dauquangthanh bundleMaintains 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 risk. Use when identifying project risks, maintaining a risk log, or preparing risk assessments for a sprint or milestone review.
- ▌ Kiss Status Report · dauquangthanh bundleDrafts 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 it. Use when preparing a project status update, creating a weekly or monthly report, or communicating project health to stakeholders.
- ▌ Kiss Tech Research · dauquangthanh bundleResearches 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 winner. Use when evaluating technology choices, comparing frameworks or databases, or before writing an ADR for a technology decision.
- ▌ Kiss Test Strategy · dauquangthanh bundleDrafts the feature-scoped test strategy — scope, risk-based test priorities, levels of testing, entry/exit criteria, environments, and tooling expectations. Produces a reviewable document the test-architect and PM anchor on. Use when planning a testing approach, defining test coverage strategy, or setting entry/exit criteria for a feature.
- ▌ Kiss Wbs Decompose · dauquangthanh bundleDecomposes the project plan's Work Breakdown Structure (WBS) into a set of feature directories, writes a stub spec.md for each WBS leaf node, and updates .kiss/feature.json to point at the first feature. Acts as the bridge between programme-level planning (kiss-project- planning) and feature-level specification (kiss-specify). Use when a Waterfall project plan exists and the team needs to fan out the WBS into individual feature folders so that kiss-specify, kiss-plan, and kiss-implement can be run feature by feature.
- ▌ Kiss XLSX Markdown · dauquangthanh bundleTranslate between Excel (.xlsx) files and Markdown with high-fidelity round-trip. Use this skill whenever the user wants to convert a spreadsheet to Markdown, review or diff a workbook as text, edit cell values or formulas in Markdown and regenerate the .xlsx, or keep a canonical text version of a workbook alongside the .xlsx. Triggers: 'xlsx to markdown', 'excel to md', 'convert this workbook to markdown', 'edit this spreadsheet as text', 'rebuild this xlsx from markdown', 'export spreadsheet as markdown tables', 'round-trip my excel file'. Preserves sheets, formulas, merged cells, number formats, fills, fonts, column widths, freeze panes, named ranges, data validations, and charts via a sidecar meta.json. Not a replacement for the base xlsx skill when building a complex financial model from scratch — use that skill for new models, and use this one for round-trip translation.
- ▌ Kiss Change Control · dauquangthanh bundleMaintains 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, rejects, or decides a change itself. Use when managing change requests, tracking scope changes, or recording CCB decisions.
- ▌ Kiss Dependency Map · dauquangthanh bundleRenders 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 circular dependencies and coupling.
- ▌
- ▌ Kiss Quality Review · dauquangthanh bundleReviews 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 code quality, checking standards compliance, or performing a pre-merge code review.
- ▌ Kiss Test Execution · dauquangthanh bundleMaintains 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 run results, tracking pass/fail status, or linking failed tests to bug reports.
- ▌ Kiss Test Framework · dauquangthanh bundleRecommends unit + integration + e2e frameworks that fit the project's language + architecture, drafts the folder layout, and lists the tooling versions. Use when choosing a test framework, setting up testing infrastructure, or defining the test toolchain for a new project or language stack.
- ▌ Kiss Vue Spa Mockup · dauquangthanh bundleScaffolds a working Vue 3 SPA mockup with Vite, TypeScript, Tailwind CSS v4, PrimeVue, Vue Router v4, Pinia, vue-i18n v9, and 3-way theming (system / light / dark). Produces a ready-to-run project directory the developer can open immediately with `npm install && npm run dev`. Interactive mode asks for the output directory, app name, views, theme, and supported locales. Use when prototyping a feature UI, bootstrapping a front-end mockup, or when the team needs a runnable Vue SPA skeleton before the production app is built.
- ▌ Kiss Arch Extraction · dauquangthanh bundleExtracts architecture from an existing codebase — containers, components, data flow, external dependencies. Produces an architecture doc that can seed new ADRs and C4 diagrams. Use when reverse-engineering a codebase, onboarding to a new project, or when architecture documentation needs to be generated from existing code.
- ▌ Kiss Security Review · dauquangthanh bundleReviews 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 posture, checking for OWASP vulnerabilities, or performing a pre-release security audit.
- ▌ Kiss Sprint Planning · dauquangthanh bundleDrafts 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 sprint, selecting backlog items for a sprint, or calculating team capacity.
- ▌ Kiss Tasks To Issues · dauquangthanh bundleConverts 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 Issues.
- ▌ Kiss Containerization · dauquangthanh bundleDrafts 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, or when the project needs Docker or Docker Compose configuration.
- ▌ Kiss Dependency Audit · dauquangthanh bundleAudits 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 security vulnerabilities in dependencies, performing a licence audit, or reviewing third-party packages for risk.
- ▌ Kiss Project Planning · dauquangthanh bundleDrafts 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 companion communication plan. Does not schedule meetings or commit a team. Use when starting a project, creating a project plan, defining milestones, or managing WBS and delivery schedule.
- ▌ Kiss React Spa Mockup · dauquangthanh bundleScaffolds a working React SPA mockup with Vite, TypeScript, Tailwind CSS v4, shadcn/ui, React Router v7, react-i18next, and a 3-way theme system (light / dark / system). Produces a ready-to-run project directory the developer can open immediately with `npm install && npm run dev`. Interactive mode asks for the output directory, app name, pages, theme default, and supported locales. Use when prototyping a feature UI, bootstrapping a front-end mockup, or when the team needs a runnable SPA skeleton before the production app is built.
- ▌ Kiss Regression Tests · dauquangthanh bundleAuthors 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 regression test, or when preventing a defect from silently reappearing in future releases.
- ▌ Kiss Feature Checklist · dauquangthanh bundleGenerates 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 meet acceptance standards.
- ▌ Kiss Observability Plan · dauquangthanh bundleDrafts 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 and observability strategy.
- ▌ Kiss Acceptance Criteria · dauquangthanh bundleAuthors Given/When/Then acceptance criteria for user stories. Drafts criteria from the spec and lets the user refine them; does not approve or sign off. Produces the single file that testers and product-owner both reference. Use when writing acceptance criteria, defining what "done" means for a story, or when user stories need Given/When/Then format.
- ▌ Kiss Data Migration Plan · dauquangthanh bundleDrafts the data migration plan for a project that replaces or upgrades a system with existing data. Covers migration strategy (Big Bang / Phased / Parallel Run / Trickle), source-to-target field mapping, data quality rules, extraction/transformation/load (ETL) outline, cutover window, rollback triggers, reconciliation approach, and post-migration validation checklist. Does not execute migrations or modify databases. Use when a Waterfall project involves migrating data from a legacy system, when a customer requires a formal migration runbook, or when data continuity is a contractual obligation.
- ▌ Kiss Deployment Strategy · dauquangthanh bundleDrafts 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 release process, or choosing between canary, blue-green, or rolling deployment patterns.
- ▌ Kiss Infrastructure Plan · dauquangthanh bundleDrafts 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, designing IaC with Terraform or Bicep, or defining network and compute topology.
- ▌ Kiss Traceability Matrix · dauquangthanh bundleBuilds and maintains a Requirements Traceability Matrix (RTM) that links every requirement (FR-NNN / NFR-NNN from the SRS) to its design section, implementation task, test case, and bug report. Supports forward traceability (requirements → delivery) and backward traceability (artefacts → requirements). Use when a Waterfall project needs to demonstrate that every requirement is designed, implemented, and tested; when a customer or auditor asks for full traceability evidence; or when performing a coverage gap analysis before a phase gate.
- ▌ Devops · dauquangthanh bundleProvides comprehensive DevOps guidance including CI/CD pipeline design, infrastructure as code (Terraform, CloudFormation, Bicep), container orchestration (Docker, Kubernetes), deployment strategies (blue-green, canary, rolling), monitoring and observability, configuration management (Ansible, Chef, Puppet), and cloud platform automation (AWS, GCP, Azure). Produces deployment scripts, pipeline configurations, infrastructure code, and operational procedures. Use when designing CI/CD pipelines, automating infrastructure, containerizing applications, setting up monitoring, implementing deployment strategies, managing configurations, or when users mention DevOps, CI/CD, infrastructure automation, Kubernetes, Docker, Terraform, deployment, monitoring, or cloud operations.
- ▌ Git Commit · dauquangthanh bundleGenerates well-structured git commit messages following conventional commit standards and best practices. Creates clear, descriptive commits with proper type prefixes (feat, fix, docs, refactor, etc.), concise subjects, and detailed bodies when needed. Use when committing code changes, creating git commits, writing commit messages, or when users mention "commit", "git commit", "commit message", "conventional commits", "changelog", or need help structuring version control messages. Ensures commits are atomic, descriptive, and follow team conventions.
- ▌ Project Planning · dauquangthanh bundleGuides comprehensive software project planning including task breakdown, estimation, sprint planning, backlog management, resource allocation, milestone tracking, and risk management. Creates user stories, acceptance criteria, project roadmaps, and work breakdown structures. Use when planning software projects, organizing sprints, breaking down features into tasks, estimating effort, managing backlogs, or when users mention "project planning", "sprint planning", "task breakdown", "roadmap", "backlog management", "user stories", or "project estimation".