kiss-u

Detect Git remote URL for GitHub integration

Scaffolds 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.

Scaffolds 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.

Scaffolds 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.

Scaffolds 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.

Translate between Word (.docx) files and Markdown with high-fidelity round-trip. Use this skill whenever the user wants to convert a Word document to Markdown, edit a .docx as text, regenerate a .docx from Markdown, diff/review Word content in git, or keep a canonical text version of a document alongside the .docx. Triggers: 'docx to markdown', 'word to md', 'convert this Word doc to markdown', 'rebuild this docx from markdown', 'edit my report in markdown', 'extract word text with formatting', 'round-trip my Word doc'. Preserves headings, lists, tables, images, footnotes, comments, tracked changes, and document styles via pandoc plus a sidecar metadata file. Not a replacement for the base docx skill when the user is authoring a new Word document from scratch — use that skill for new content, and use this one for round-trip translation.

Translate between PowerPoint (.pptx) files and Markdown with high-fidelity round-trip. Use this skill whenever the user wants to convert a deck to Markdown, edit a deck as Markdown, regenerate a .pptx from Markdown, diff/review slide content as text, or version-control a presentation. Triggers: 'convert slides to markdown', 'edit this deck in markdown', 'pptx to md', 'md to pptx', 'round-trip my presentation', 'export slides as text', 'rebuild this pptx from markdown', or anytime a .pptx and a .md file both appear in the task. Not a replacement for the base pptx skill when the user is creating a visually rich deck from scratch — use that skill for new designs, and use this one for round-trip translation.

Translate 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.

Translate between Word (.docx) files and Markdown with high-fidelity round-trip. Use this skill whenever the user wants to convert a Word document to Markdown, edit a .docx as text, regenerate a .docx from Markdown, diff/review Word content in git, or keep a canonical text version of a document alongside the .docx. Triggers: 'docx to markdown', 'word to md', 'convert this Word doc to markdown', 'rebuild this docx from markdown', 'edit my report in markdown', 'extract word text with formatting', 'round-trip my Word doc'. Preserves headings, lists, tables, images, footnotes, comments, tracked changes, and document styles via pandoc plus a sidecar metadata file. Not a replacement for the base docx skill when the user is authoring a new Word document from scratch — use that skill for new content, and use this one for round-trip translation.

Translate between PowerPoint (.pptx) files and Markdown with high-fidelity round-trip. Use this skill whenever the user wants to convert a deck to Markdown, edit a deck as Markdown, regenerate a .pptx from Markdown, diff/review slide content as text, or version-control a presentation. Triggers: 'convert slides to markdown', 'edit this deck in markdown', 'pptx to md', 'md to pptx', 'round-trip my presentation', 'export slides as text', 'rebuild this pptx from markdown', or anytime a .pptx and a .md file both appear in the task. Not a replacement for the base pptx skill when the user is creating a visually rich deck from scratch — use that skill for new designs, and use this one for round-trip translation.

Translate 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.

Snapshots the current state of requirements, design, or test artefacts as a named, immutable baseline under docs/baselines/. Tags the git repository at the same point so the snapshot is permanently reachable in version history. Pairs with kiss-change- control: the baseline is the "from" state any change request must reference. Use after a Requirements (SRR) or Architecture (CDR) phase-gate passes, when a customer requests a formal freeze, or when a change-control board (CCB) needs a reference snapshot.

Drafts 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.

Drafts the operations and support hand-over package for a feature or release. Assembles the runbook index, on-call rota seed, support escalation matrix, known limitations, training-material checklist, warranty / hypercare period definition, and knowledge-transfer session plan. Produces a self-contained package the development team hands to the operations / support team at go-live. Use at the end of a Waterfall project after the Go/No-Go gate passes, when transitioning from project to BAU (business-as-usual) support, or when a contractual hand-over document is required.

Authors a Waterfall phase-exit checklist and sign-off page for a named gate (Requirements, Architecture / CDR, Test Readiness / TRR, Operational Readiness / ORR, or Go-Live). Verifies entry and exit criteria against upstream artefacts, lists all required deliverables with their status, and produces a dated gate record the project manager uses to decide whether the project may proceed to the next phase. Use when a Waterfall project reaches a phase boundary, when a customer or PMO requires formal gate sign-off, or when conducting a Milestone Review.

Aggregates all feature specs into a single IEEE 29148:2018-aligned System / Software Requirements Specification (SRS). Numbers every functional requirement (FR-NNN) and non-functional requirement (NFR-NNN), establishes a requirements baseline, and produces the sign-off cover sheet. Use when a Waterfall project needs a formal consolidated SRS before architecture design begins, when a regulatory or contractual deliverable demands a numbered requirement set, or when the project requires traceability from business needs to design.

Builds 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.

Drafts the User Acceptance Testing (UAT) plan for a feature or release. UAT is a customer-owned phase distinct from system testing: it verifies that the delivered system meets business objectives in a production-like environment with real or representative users. Produces scope, entry/exit criteria, environments, participant roster, test scenarios (business-workflow level), execution schedule, sign-off ledger, and defect escalation rules. Does not facilitate the UAT session itself. Use when a Waterfall project approaches the verification phase, when a customer contract requires formal UAT sign-off, or when distinguishing UAT from QA system testing.

Decomposes 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.

Snapshots the current state of requirements, design, or test artefacts as a named, immutable baseline under docs/baselines/. Tags the git repository at the same point so the snapshot is permanently reachable in version history. Pairs with kiss-change- control: the baseline is the "from" state any change request must reference. Use after a Requirements (SRR) or Architecture (CDR) phase-gate passes, when a customer requests a formal freeze, or when a change-control board (CCB) needs a reference snapshot.

Drafts 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.

Drafts the operations and support hand-over package for a feature or release. Assembles the runbook index, on-call rota seed, support escalation matrix, known limitations, training-material checklist, warranty / hypercare period definition, and knowledge-transfer session plan. Produces a self-contained package the development team hands to the operations / support team at go-live. Use at the end of a Waterfall project after the Go/No-Go gate passes, when transitioning from project to BAU (business-as-usual) support, or when a contractual hand-over document is required.

Authors a Waterfall phase-exit checklist and sign-off page for a named gate (Requirements, Architecture / CDR, Test Readiness / TRR, Operational Readiness / ORR, or Go-Live). Verifies entry and exit criteria against upstream artefacts, lists all required deliverables with their status, and produces a dated gate record the project manager uses to decide whether the project may proceed to the next phase. Use when a Waterfall project reaches a phase boundary, when a customer or PMO requires formal gate sign-off, or when conducting a Milestone Review.

Aggregates all feature specs into a single IEEE 29148:2018-aligned System / Software Requirements Specification (SRS). Numbers every functional requirement (FR-NNN) and non-functional requirement (NFR-NNN), establishes a requirements baseline, and produces the sign-off cover sheet. Use when a Waterfall project needs a formal consolidated SRS before architecture design begins, when a regulatory or contractual deliverable demands a numbered requirement set, or when the project requires traceability from business needs to design.

Builds 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.

Drafts the User Acceptance Testing (UAT) plan for a feature or release. UAT is a customer-owned phase distinct from system testing: it verifies that the delivered system meets business objectives in a production-like environment with real or representative users. Produces scope, entry/exit criteria, environments, participant roster, test scenarios (business-workflow level), execution schedule, sign-off ledger, and defect escalation rules. Does not facilitate the UAT session itself. Use when a Waterfall project approaches the verification phase, when a customer contract requires formal UAT sign-off, or when distinguishing UAT from QA system testing.

Decomposes 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.

Creates or updates the project standards from interactive or provided principle inputs, ensuring all dependent templates stay in sync. Use when defining coding standards, setting project conventions, or establishing style guidelines for a new or existing project.

Creates or updates the project standards from interactive or provided principle inputs, ensuring all dependent templates stay in sync. Use when defining coding standards, setting project conventions, or establishing style guidelines for a new or existing project.

Authors 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.

Authors Architecture Decision Records (ADRs) in the Michael Nygard template. One ADR per file, auto-numbered, lives under docs/decisions/. Records the decision the user made — does not make decisions. Use when recording a technical choice, documenting why a technology or design approach was selected, or when a decision needs a permanent, reviewable record.

Generates API documentation from source code: lists endpoints / RPC methods / queue topics with their schemas and auth. Works backward from routes + OpenAPI / proto / gql definitions. Use when documenting an API, generating endpoint reference docs, or when the project needs OpenAPI, gRPC, or GraphQL schemas documented.

Extracts 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.

Captures architecture inputs — quality attributes ranking, hard constraints, team context, operational envelope, integration surface, deployment preferences — into a single intake artefact the architect works from. Use when starting system design, capturing requirements for an architecture, or before producing ADRs and C4 diagrams.

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 or commit a team to deliver. Use when managing a product backlog, adding user stories, reprioritising features, or preparing for sprint planning.

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 testing, or when a failing test needs a formal bug report.

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 for a bug-fix sprint.

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 architecture diagrams, visualising system structure, or when the project needs Context, Container, or Component-level views.

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, rejects, or decides a change itself. Use when managing change requests, tracking scope changes, or recording CCB decisions.

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 log after a release, or tracking which commits fixed which bugs.