@jakkrichm/create-nexus-devflow 2.2.2 → 2.6.0

package/template/.claude/skills/50-verify/SKILL.md

@@ -1,62 +0,0 @@
----
-name: 50-verify
-description: "[devflow][D] Verify stage in DevFlow 2.0 - perform senior QA review, record evidence, and decide pass or return-to-implement."
----
-
-# Phase 50: Verify Quality
-
-Review implementation quality, run multi-lane validation, produce a verification report, and route the task forward or back to implementation.
-
-## Usage
-
-```text
-50-verify {ID}
-```
-
-## Markdown-First Contract
-
-Use `50-verify.md` as the primary verification artifact.
-Use `50-verify-impact.md` as an optional companion artifact when the run changes behavior, touches core logic, crosses integration boundaries, or needs explicit rollback and client impact analysis.
-
-## Process & Quality Gates (Two-Stage Review Pattern)
-
-### Stage 1: Spec Fidelity & Acceptance Criteria Gate
-Before evaluating technical code metrics, verify that the implementation faithfully delivers what was specified:
-1. **Acceptance Criteria Validation**: Cross-check each Acceptance Criterion (AC-1, AC-2, ...) in `20-spec.md` or `current-feature.md` and verify concrete evidence of completion.
-2. **Done-When Observable Verification**: Check that all observable conditions ("Done when...") are satisfied in the running application or test suite.
-3. **Scope Discipline**: Ensure zero scope creep (no unrequested features added) and no unfulfilled functional requirements.
-4. **Boundary & Negative Scenarios**: Verify unhappy paths, empty inputs, and error states defined in the specification.
-
-### Stage 2: Code Quality, Security & Architecture Gate
-Execute multi-lane technical verification across all essential quality dimensions:
-
-1. **Lane 1: Typecheck & Static Code Quality**:
-   - Run typecheck and static analysis (`tsc --noEmit`, `npm run lint`).
-2. **Lane 2: Automated Test Suites (Strict TDD Gate)**:
-   - Run automated unit and integration tests (`npm test`).
-   - Confirm 100% test pass rate with zero disabled or skipped tests.
-3. **Lane 3: Scrutinize QA & Edge Cases Review**:
-   - **Boundary Conditions**: Check empty inputs, 0/1 counts, off-by-one errors.
-   - **Null / Undefined Safety**: Verify nullish handling and strict type invariants.
-   - **Error Handling & Propagation**: Verify errors provide actionable diagnostics without swallowing.
-4. **Lane 4: Security & Hygiene Audit**:
-   - **Secrets Check**: Ensure no hardcoded credentials or API keys exist.
-   - **Input Sanitization**: Ensure parameterized queries and validated inputs.
-5. **Lane 5: Findings Ledger State Machine (`findings.md`)**:
-   - Inspect `devflow/context/findings.md`.
-   - **P0/P1 HARD GATE**: Any Finding of severity `P0` or `P1` in `open` or `fixed` status unconditionally blocks pass.
-6. **Lane 6: Manual Scenario Proof**:
-   - Provide clear manual verification instructions: "Where to go", "What to run/click", "What to expect".
-
-### 2. Decision & Route
-
-- **Pass**: Both Stage 1 and Stage 2 pass with 0 blockers -> Route to `60-report {ID}`.
-- **Fail**: Either Stage 1 or Stage 2 fails -> Route back to `40-execute {ID}` with exact failure evidence and remediation steps.
-
-## Output
-
-Report:
-- **Stage 1 Verdict**: Spec Fidelity & Acceptance Criteria status
-- **Stage 2 Verdict**: Technical Multi-lane quality & security matrix
-- Evidence commands and outputs
-- Next command: `60-report {ID}` (if pass) or `40-execute {ID}` (if fail)

package/template/.claude/skills/60-report/SKILL.md

@@ -1,57 +0,0 @@
----
-name: 60-report
-description: "[devflow][D] Report stage in DevFlow 2.0 - produce standardized markdown summary report with retrospective lessons learned."
-argument-hint: "{running-id or workspace path}"
----
-
-# Phase 60: Report
-
-$ARGUMENTS
-
-Produce the final human-friendly summary of the full running flow in Markdown (`60-report.md`) with retrospective lessons learned, findings summary, and release digest.
-
-## Usage
-
-```text
-60-report {running-id or workspace path}
-```
-
-## Markdown-First Contract
-
-Write the primary stage artifact to:
-
-```text
-devflow/context/current-run/60-report.md
-```
-
-> [!IMPORTANT]
-> **No Auto-Generated HTML**: ห้ามสร้างไฟล์ `60-report.html` แบบอัตโนมัติในขั้นตอนนี้! ระบบจะสร้างเฉพาะ `60-report.md` เท่านั้น หากต้องการดู HTML Report ให้เรียกคำสั่งแยก: `/report:html`
-
-## Process
-
-### 1. Gather Full Run Context & Verification Evidence
-Read all relevant stage artifacts:
-- `10-define.md`
-- `20-spec.md`
-- `30-plan.md`
-- `40-execute.md`
-- `50-verify.md`
-
-### 2. Retrospective Lessons Learned & Gotchas (Insight Extraction)
-Extract durable insights from the completed run:
-- **Reusable Patterns**: Design choices or implementations that future runs should mirror.
-- **Gotchas & Pitfalls**: Unforeseen issues or quirks encountered during execution.
-- **Unresolved Follow-ups**: Route any residual out-of-scope ideas to `devflow/ideas.md`.
-
-### 3. Produce Standardized Report (`60-report.md`)
-Structure the report in **Thai (`th`)**:
-1. **Executive Summary**: ปัญหาและแนวทางแก้ไข
-2. **Delivery Scope**: รายการฟีเจอร์และคอมโพเนนต์ที่ส่งมอบ
-3. **Verification Evidence Snapshot**: ผลการทดสอบทุก Lane
-4. **Retrospective & Lessons Learned**: บทเรียนและข้อควรระวัง
-5. **Manual Try Guide**: ขั้นตอนสำหรับมนุษย์ทดสอบระบบ
-
-## Next Workflow Recommendation
-
-- **Primary**: `70-deliver {ID}`
-- **Optional Standalone HTML**: `/report:html`

package/template/.claude/skills/70-deliver/SKILL.md

@@ -1,72 +0,0 @@
----
-name: 70-deliver
-description: "[devflow][D] Deliver stage in DevFlow 2.0 - package verified work for delivery, archive run to categorized history, git merge, PR, or deployment."
-argument-hint: "{running-id or workspace path}"
----
-
-# Phase 70: Deliver
-
-$ARGUMENTS
-
-Package approved work for delivery after the report stage has captured the final verified story. Archives the active run from `devflow/context/current-run/` to `devflow/history/{features|fixes|rollbacks}/{xxx-slug}/`, updates `HISTORY.md` and `CHANGELOG.md`, executes pre-flight smoke checks, performs conventional git commit & merge, and closes the run.
-
-## Usage
-
-```text
-70-deliver {id or workspace path}
-```
-
-## Markdown-First Contract
-
-Write the primary stage artifact to:
-
-```text
-devflow/context/current-run/70-deliver.md
-```
-
-## Process & Quality Gates
-
-### 0. Step 0 Safety Pass & Findings Ledger Gate
-
-Before packaging, merging, or delivering:
-
-1. **Findings Ledger Blockers**:
-   - Inspect `devflow/context/findings.md`.
-   - No Finding of severity `P0` or `P1` in `open` or `fixed` status is permitted.
-   - `fixed` still blocks release until reviewed and closed in `50-verify`.
-2. **Pre-flight & Deployment Smoke Validation**:
-   - Verify environment variables and configuration parameters.
-   - Run production build or package smoke check (`npm run build` or `npm run test:package`).
-   - Validate that clean state exists with no untracked experimental files.
-3. **2-Stage Approval Separation**:
-   - Consent to merge into `main` is strictly separate from consent to `git push` to remote or deploy.
-
-### 1. Changelog & SemVer Version Bump
-
-1. Calculate next version according to **Semantic Versioning (SemVer)**:
-   - `Major`: Breaking architectural changes, removed public APIs
-   - `Minor`: New backward-compatible features added
-   - `Patch`: Bug fixes, optimizations, documentation
-2. Append new release entry to `CHANGELOG.md` in [Keep a Changelog](https://keepachangelog.com/en/1.1.0/) format (`Added`, `Changed`, `Fixed`, `Removed`, `Security`).
-
-### 2. Conventional Commit & Git Merge
-
-1. Stage all release and tracking files.
-2. Commit with conventional format: `chore(release): release {version}` or `feat({scope}): {summary}`.
-3. Squash-merge to base branch (`main`) with explicit user approval.
-
-### 3. Archive Run Folder to Categorized History
-
-1. Determine Category (`features`, `fixes`, `rollbacks`).
-2. Move directory `devflow/context/current-run/` ➔ `devflow/history/{category}/{xxx-slug}/`.
-3. Clean resolved findings (`closed`, `accepted`, `invalid`) from `devflow/context/findings.md` and append to the release notes.
-4. Append entry to `devflow/history/HISTORY.md` linking to `history/{category}/{xxx-slug}/60-report.md`.
-
-### 4. Update Workspace State
-
-Set `devflow/context/current-stage.md` to:
-- `Active Discovery ID`: `None`
-- `Active Running ID`: `None (Idle)`
-- `Current Stage`: `Idle (Ready for new run)`
-- `Last Completed Run`: `{ID} ({YYYY-MM-DD})`
-- `Last Updated`: `{YYYY-MM-DD}`