Skip to content

Releases: aihxp/stack-ready

v1.1.12

06 May 12:55

Choose a tag to compare

Documentation-only patch. Adds first-class support for pi and OpenClaw via the Agent Skills standard. The suite now positions explicitly as agentskills.io-compatible: any harness that parses SKILL.md frontmatter natively runs every ready-suite skill first-class, with no per-tool integration. pi and OpenClaw both load skills from the neutral ~/.agents/skills/ path defined by the standard, so future AgentSkills-compatible harnesses inherit support for free.

Changed

  • Frontmatter: compatible_with now lists pi, openclaw, and any-agentskills-compatible-harness (the latter replaces the older any-agent-with-skill-loading value for tighter standards-level signaling).
  • SUITE.md: install-locations table adds rows for pi, OpenClaw, and the neutral Agent Skills path; new "Standards" section names the standard and the verified harnesses (Claude Code, Codex, Cursor, Windsurf, pi, OpenClaw).
  • Hub install.sh / uninstall.sh (in aihxp/ready-suite): detect pi (~/.pi/) and OpenClaw (~/.openclaw/), write to the neutral ~/.agents/skills/ path. No regressions on the existing Claude Code / Codex / Cursor flow.

Why a patch, not a minor

The skill's behavior, references, and workflow are unchanged. Only the frontmatter compatible_with list, SUITE.md, and the README install section move; the version + updated frontmatter fields tick. Per the suite versioning discipline, patch-level is the honest bucket for documentary-only standards-compliance signaling.

v1.1.11

06 May 16:10

Choose a tag to compare

Documentation-only patch. Suite-wide SUITE.md refresh introducing the new orchestration tier and the eleventh sibling, kickoff-ready v1.0.0. kickoff-ready sequences the ten core-suite specialists for greenfield projects from raw user intent: it triggers from a fresh idea ("kickoff," "I have an idea help me ship it") and invokes prd-ready -> architecture-ready -> roadmap-ready -> stack-ready -> repo-ready -> production-ready -> deploy-ready -> observe-ready -> (launch-ready || harden-ready), verifying each artifact on disk before advancing. It produces only .kickoff-ready/PROGRESS.md; it never produces specialist content. No behavioral changes to this skill.

Changed

  • SUITE.md: new "orchestration" tier introduced as the first column of the four-tier diagram; new kickoff-ready row in the per-skill table; updated dependency-flow text; new composition principle 8 ("Orchestration is one-way: kickoff-ready knows about specialists; specialists do not know about kickoff-ready"); known-good versions table now lists eleven skills.

Why a patch, not a minor

The skill's behavior, frontmatter contract, and reference library are unchanged. Only the cross-sibling SUITE.md is touched and the version + updated frontmatter fields tick. Per the suite versioning discipline, patch-level is the honest bucket for documentary-only sibling-ship tracking.

v1.1.10

29 Apr 20:06

Choose a tag to compare

Documentation-only patch. Removes the Mirror Box dogfood track from the ready-suite. The aihxp/mirror-box repo has been archived; the canonical-dogfood section in SUITE.md is gone; per-skill dogfood/ folders are deleted.

Changed

  • SUITE.md no longer carries the "Canonical dogfood target: Mirror Box" section. Byte-identical sync across all ten siblings.
  • dogfood/ folder removed from this repo.

Why

The Mirror Box reference implementation required real infrastructure (Fastify + OTel + Fly.io + Honeycomb account) to fully exercise. The user wanted a skill suite, not a project that demands a particular hosted stack. Removing Mirror Box restores that posture: every skill stands on its own SKILL.md plus references; downstream consumers compose via the artifact contracts the skills describe, without depending on a shared hosted exemplar.

The interop standard is unchanged. Skills still produce .{skill}-ready/*.md artifacts; downstream siblings still read them. The contract holds without a canonical demo.


v1.1.9

24 Apr 15:02

Choose a tag to compare

Documentation-only patch. Suite-wide SUITE.md refresh introducing the canonical dogfood target: aihxp/mirror-box. Adds a new "Canonical dogfood target" section to SUITE.md with links to the ten per-skill dogfood artifacts. Adds composition principle #7 codifying the byte-identical-SUITE.md invariant across siblings. No behavioral changes to the skill.

Changed

  • SUITE.md: new "Canonical dogfood target: Mirror Box" section with artifact links.
  • SUITE.md: composition principles now include #7 (byte-identical SUITE.md across siblings).
  • SUITE.md: version table bumped; all ten skills reflect the coordinated sync.

Why a patch, not a minor

Same rationale as prior x.y.z patches: the skill's behavior, frontmatter contract, and reference library are unchanged. Only the cross-sibling SUITE.md is touched. Per the suite versioning discipline, patch-level is the honest bucket for documentary-only sibling-ship tracking.

v1.1.8

23 Apr 22:37

Choose a tag to compare

Documentation-only patch. Reflects the arrival of harden-ready v1.0.0 (https://github.com/aihxp/harden-ready) as a live sibling in the ready-suite. harden-ready is the tenth and final core-suite skill; its v1.0.0 release completes the shipping tier alongside deploy-ready, observe-ready, and launch-ready, and completes the ready-suite across planning (four), building (two), and shipping (four) tiers. harden-ready owns post-deploy adversarial review, OWASP Top 10 walkthroughs (Web / API / LLM), compliance control-to-code mapping (SOC 2 / HIPAA / PCI-DSS / GDPR), pen-test preparation and retest discipline, responsible-disclosure program design beyond SECURITY.md, and class-not-instance post-incident hardening. No behavioral changes to this skill.

Changed

  • SUITE.md updated to list harden-ready at 1.0.0 alongside the coordinated one-patch bump across every live sibling. Copy remains byte-identical across every live sibling.
  • SKILL.md frontmatter version bumped to 1.1.8. No content change beyond the version tag.

Why a patch, not a minor

The skill's behavior, frontmatter contract, and reference library are unchanged. Only the cross-sibling SUITE.md is touched to track a new sibling's release. Per the suite versioning discipline, patch-level is the honest bucket for documentary-only sibling-ship tracking.

v1.1.4 Sibling sync: launch-ready 1.0.0 live

23 Apr 07:38

Choose a tag to compare

Documentation-only patch. SUITE.md updated to reflect launch-ready v1.0.0. Shipping tier is now complete.

v1.1.3 Sibling sync: repo-ready 1.6.0 live

23 Apr 07:25

Choose a tag to compare

v1.1.3 (2026-04-23)

Documentation-only patch. Reflects the arrival of repo-ready v1.6.0 as a live sibling in the ready-suite with its suite-membership retrofit (frontmatter interop fields, SUITE.md, Unicode cleanup). No behavioral changes to the skill.

Changed

  • SUITE.md known-good versions table updated: repo-ready now shows version 1.6.0 and its repo URL instead of "See its CHANGELOG."
  • SKILL.md frontmatter version bumped to 1.1.3. No content change beyond the version tag.

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog.

v1.1.2 Sibling sync: observe-ready 1.0.0 live

23 Apr 07:28

Choose a tag to compare

[1.1.2] - 2026-04-22

Documentation-only patch. Reflects the arrival of observe-ready v1.0.0 (https://github.com/aihxp/observe-ready) as a live sibling in the ready-suite. No behavioral changes to the skill.

Changed

  • SUITE.md updated to list observe-ready at 1.0.0 alongside production-ready 2.5.3, stack-ready 1.1.2, and deploy-ready 1.0.1. Copy remains byte-identical across every live sibling.
  • SKILL.md frontmatter version bumped to 1.1.2. No content change beyond the version tag.

Why a patch

Same rationale as 1.1.1: only the cross-sibling SUITE.md and the version stamps are touched. The skill's behavior, references, and scoring contract are unchanged.


v1.1.1 Sibling sync: deploy-ready 1.0.0 live

23 Apr 07:28

Choose a tag to compare

[1.1.1] - 2026-04-22

Documentation-only patch. Reflects the arrival of deploy-ready v1.0.0 (https://github.com/aihxp/deploy-ready) as a live sibling in the ready-suite. No behavioral changes to the skill.

Added

  • SUITE.md at repo root. Byte-identical copy of the suite map shared across every ready-suite sibling. Stack-ready did not previously ship one; this patch closes that gap so the byte-identical invariant holds across all live siblings (production-ready 2.5.2, stack-ready 1.1.1, deploy-ready 1.0.0).

Changed

  • SKILL.md frontmatter version bumped to 1.1.1. Template version stamps in DECISION.md, STATE.md, and the staleness-check output updated to match. No content change beyond the version tag.

Why a patch, not a minor

The skill's behavior, references, and scoring contract are unchanged. Only the cross-sibling SUITE.md and the version stamps are touched. Per the suite versioning discipline, patch-level is the honest bucket for documentary-only sibling-ship tracking.


v1.1.0: Research-driven refresh

22 Apr 10:35

Choose a tag to compare

Research-driven refresh. Six parallel research threads (framework, data, auth/payments/email, hosting/observability/queues, decision methodology, cross-language) produced a consolidated dossier and surgical updates across every reference file.

No architectural changes. All edits are evidence-backed against primary sources captured in references/RESEARCH-2026-04.md (~150 verified URLs).

What changed

Added

  • references/RESEARCH-2026-04.md (~30K tokens) as the single source-of-truth dossier for 1.1.0's refresh.
  • Scoring framework split: Ecosystem depth (8%) + Ecosystem trajectory (7%) replaces single Ecosystem / maturity (15%).
  • New Exit cost / reversibility (7%) scoring dimension, first-class now (used to be tradeoff-narrative-only).
  • "When to skip the scoring pass entirely" section acknowledging the McKinley/DHH/Levels anti-scoring camp.
  • Pre-flight question 7 (Reversibility posture): Exploratory / Committed / Foundational, with per-dimension reversibility defaults.
  • DECISION.md template: Prior art and analogous picks section (Rust RFC influence).
  • 5 new cross-domain bundles: Cloudflare-native, Post-Cloud Rails, Phoenix LiveView, Django + HTMX + Alpine, TALL / Laravel + Livewire.
  • Sync-engine anti-pairing (Convex + Liveblocks over same state, Supabase Realtime + Convex).
  • LLM observability subsection (Braintrust, Langfuse, Helicone, LangSmith, Phoenix).
  • TypeScript backend subsection (Hono leads edge/multi-runtime; Fastify Node-native; Elysia Bun-specific).
  • JS runtime sub-axis (Node 24 LTS / Node 22 LTS / Bun / Deno 2 production posture).

Staleness fixes

  • Auth.js folded into Better Auth (Sept 2025) - Auth.js downgraded to 5 for new projects.
  • Remix v2 merged into React Router v7 (Nov 2024) - renames across domain-stacks.md.
  • Stripe acquired Lemon Squeezy (July 2024) and launched Stripe Managed Payments (private beta April 2025).
  • Prisma 7 (late 2025) removed the Rust query engine; historical bundle/cold-start penalties now stale.
  • Neon acquired by Databricks (~$1B, May 2025); PlanetScale launched Postgres on Neki (Sept 2025).
  • Redis fragmented (2024): Valkey / DragonflyDB / Upstash captured the "Redis-compatible" landscape.
  • Highlight.io acquired by LaunchDarkly, shuts down Feb 28, 2026.
  • Bun acquired by Anthropic (Dec 2025); Rising Stars 2025 #1 build tool.
  • Vercel Fluid Compute + Active CPU (April 2025): up to 90% cost cut for idle-heavy workloads.
  • Cloudflare Developer Platform: D1, Queues, Hyperdrive GA (April 2024); Workflows GA (2025); DO with SQLite on free tier.

Changed

  • Default weight vector rebalanced: DX 20 / Scale 13 / Cost 13 / EcoDepth 8 / EcoTraj 7 / Exit 7 / Ops 12 / Compliance 10 / Hireability 10.
  • SendGrid scoring dropped from 7 to 6 (free tier removed).
  • Grafana Cloud bumped from 7 to 8 (primary Datadog migration target, ~40% savings documented).
  • Cloudflare bumped from 7 to 8-9 depending on workload (Dev Platform GA).

Evidence base (sample)

  • Stack Overflow Developer Survey 2024-2025.
  • State of JS 2024 (Astro +39 pts satisfaction over Next.js).
  • JavaScript Rising Stars 2024 and 2025.
  • DB-Engines ranking trends (Postgres top climber in 4 of 6 recent months).
  • ThoughtWorks Tech Radar Vol 31 and 34.
  • State of Django 2025 (HTMX 24%, Alpine 14%).
  • State of Laravel 2025 (Livewire 62%, Inertia 48%).
  • Grafana Labs 50+ Datadog migration case studies.
  • 37signals cloud exit: $10M+ over five years.
  • Convex's own migration from Aurora MySQL to PlanetScale Postgres.

Did not change (explicitly)

  • 9-step workflow, 4-tier completion structure, Mode A/B/C/D detection unchanged.
  • Have-nots list unchanged.
  • Compliance-as-filter principle unchanged.

Full changelog in CHANGELOG.md. Evidence in references/RESEARCH-2026-04.md.