@yaawn/workflow 0.0.0-stage → 0.4.0

package/github/ISSUE_TEMPLATE/yaawn-bug-report.md

@@ -0,0 +1,59 @@
+---
+about: Create a report to help us improve
+assignees: ""
+labels: ["Yaawn: Bug", "Yaawn: To Be Refined"]
+name: Yaawn Bug report
+projects: []
+title: ""
+---
+
+## Summary
+
+<!-- Describe in short easy to understand words the problem (not the solution). -->
+
+## Steps to reproduce
+
+1. ...
+
+## What is the current behavior?
+
+## What is the expected behavior?
+
+## Relevant logs and/or screenshots
+
+## Environment
+
+- System:
+- App-Version:
+- OS:
+- Browser:
+- Browser-Version:
+- Screen Resolution:
+
+## Implementation Plan
+
+<!-- How? Talk about this during planning part 3 or during work. -->
+
+### Human Readable
+
+### Open Questions
+
+| #   | Questions | Owner | Answer |
+| --- | --------- | ----- | ------ |
+|     |           |       |        |
+
+### Design Decisions
+
+<!-- Document decisions here that were made during planning or a grilling session. -->
+
+| #   | Decision | Choice | Rationale |
+| --- | -------- | ------ | --------- |
+|     |          |        |           |
+
+### Files to Change
+
+<!-- Bullet list of repo-relative paths of every file the implementation will change. -->
+
+### LLM Plan
+
+<!-- The plan is written here by /yaawn-save-plan. The Definition of Done lives in `.yaawn/yaawn-definition-of-done.md`. -->

package/github/ISSUE_TEMPLATE/yaawn-other.md

@@ -0,0 +1,38 @@
+---
+about: Work that matches none of the four types.
+assignees: ""
+labels: ["Yaawn: Other", "Yaawn: To Be Refined"]
+name: Yaawn Other
+projects: []
+title: ""
+---
+
+## Goal
+
+## Implementation Plan
+
+<!-- How? Talk about this during planning part 3 or during work. -->
+
+### Human Readable
+
+### Open Questions
+
+| #   | Questions | Owner | Answer |
+| --- | --------- | ----- | ------ |
+|     |           |       |        |
+
+### Design Decisions
+
+<!-- Document decisions here that were made during planning or a grilling session. -->
+
+| #   | Decision | Choice | Rationale |
+| --- | -------- | ------ | --------- |
+|     |          |        |           |
+
+### Files to Change
+
+<!-- Bullet list of repo-relative paths of every file the implementation will change. -->
+
+### LLM Plan
+
+<!-- The plan is written here by /yaawn-save-plan. The Definition of Done lives in `.yaawn/yaawn-definition-of-done.md`. -->

package/github/ISSUE_TEMPLATE/yaawn-refactor.md

@@ -0,0 +1,38 @@
+---
+about: Changes that users do not see.
+assignees: ""
+labels: ["Yaawn: Refactor", "Yaawn: To Be Refined"]
+name: Yaawn Refactor
+projects: []
+title: ""
+---
+
+## Goal
+
+## Implementation Plan
+
+<!-- How? Talk about this during planning part 3 or during work. -->
+
+### Human Readable
+
+### Open Questions
+
+| #   | Questions | Owner | Answer |
+| --- | --------- | ----- | ------ |
+|     |           |       |        |
+
+### Design Decisions
+
+<!-- Document decisions here that were made during planning or a grilling session. -->
+
+| #   | Decision | Choice | Rationale |
+| --- | -------- | ------ | --------- |
+|     |          |        |           |
+
+### Files to Change
+
+<!-- Bullet list of repo-relative paths of every file the implementation will change. -->
+
+### LLM Plan
+
+<!-- The plan is written here by /yaawn-save-plan. The Definition of Done lives in `.yaawn/yaawn-definition-of-done.md`. -->

package/github/ISSUE_TEMPLATE/yaawn-spike.md

@@ -0,0 +1,16 @@
+---
+about: Do some limited research.
+assignees: ""
+labels: ["Yaawn: Spike", "Yaawn: To Be Refined"]
+name: Yawn Spike
+projects: []
+title: ""
+---
+
+<!-- What question should be answered by the spike? -->
+
+## Question
+
+<!-- Please document your answer for others -->
+
+## Answer

package/github/ISSUE_TEMPLATE/yaawn-story.md

@@ -0,0 +1,56 @@
+---
+about: Stories introduce new features.
+assignees: ""
+labels: ["Yaawn: Story", "Yaawn: To Be Refined"]
+name: Yaawn Story
+projects: []
+title: ""
+---
+
+<!-- Who and Why. Talk about this during Refinement. -->
+
+As a ROLE, I want to GOAL, so that BENEFIT.
+
+<!--
+  Behavioral only. Written in third person about the user. No implementation details.
+  Each criterion must be testable by a non-developer. Describe what the user
+  experiences, not how it is built.
+-->
+
+## Acceptance Criteria
+
+- [ ] **Given** SITUATION/ROLE/OTHER
+  - [ ] **When** ACTION
+    - [ ] **then** REACTION
+  - [ ] **When** ACTION
+    - [ ] **then** REACTION
+
+## Screenshots, Mockups
+
+## Implementation Plan
+
+<!-- How? Talk about this during planning part 3 or during work. -->
+
+### Human Readable
+
+### Open Questions
+
+| #   | Questions | Owner | Answer |
+| --- | --------- | ----- | ------ |
+|     |           |       |        |
+
+### Design Decisions
+
+<!-- Document decisions here that were made during planning or a grilling session. -->
+
+| #   | Decision | Choice | Rationale |
+| --- | -------- | ------ | --------- |
+|     |          |        |           |
+
+### Files to Change
+
+<!-- Bullet list of repo-relative paths of every file the implementation will change. -->
+
+### LLM Plan
+
+<!-- The plan is written here by /yaawn-save-plan. The Definition of Done lives in `.yaawn/yaawn-definition-of-done.md`. -->

package/package.json

@@ -1,6 +1,35 @@
 {
   "name": "@yaawn/workflow",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.4.0",
+  "description": "Installs .agents/ skill files (skills, instructions, output-styles) into your project via `npx @yaawn/workflow`.",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/markusfalk/yaawn.git",
+    "directory": "packages/workflow"
+  },
+  "publishConfig": {
+    "access": "public"
+  },
+  "bin": {
+    "workflow": "scripts/install.js"
+  },
+  "scripts": {
+    "release:dry-run": "node release/release-installer.mjs --dry-run"
+  },
+  "files": [
+    "scripts/",
+    "config/",
+    "agents/",
+    "!agents/**/*.test.ts",
+    "yaawn/",
+    "github/"
+  ],
+  "optionalDependencies": {
+    "@yaawn/workflow-darwin-arm64": "0.4.0",
+    "@yaawn/workflow-darwin-x64": "0.4.0",
+    "@yaawn/workflow-linux-x64": "0.4.0",
+    "@yaawn/workflow-linux-arm64": "0.4.0",
+    "@yaawn/workflow-win32-x64": "0.4.0"
+  }
+}

package/scripts/install.js

@@ -0,0 +1,73 @@
+#!/usr/bin/env node
+"use strict";
+
+/**
+ * Launcher for @yaawn/workflow (`npx @yaawn/workflow`).
+ *
+ * The installer itself is a Go binary shipped in a per-platform optional
+ * dependency (`<package name>-<platform>`, e.g. `@yaawn/workflow-<platform>`).
+ * The package name is read from this package's package.json, so a rename only
+ * touches package.json. This shim finds the binary
+ * for the current platform and runs it with the package root, so the binary
+ * can read the bundled config and payload.
+ */
+
+const path = require("path");
+const { spawnSync } = require("child_process");
+const { name: packageName } = require("../package.json");
+
+const BINARY_NAME = "workflow";
+
+const PLATFORM_KEYS = {
+  "darwin/arm64": "darwin-arm64",
+  "darwin/x64": "darwin-x64",
+  "linux/x64": "linux-x64",
+  "linux/arm64": "linux-arm64",
+  "win32/x64": "win32-x64",
+};
+
+const currentPlatform = `${process.platform}/${process.arch}`;
+
+function fail(message) {
+  process.stderr.write(`${BINARY_NAME}: ${message}\n`);
+  process.exit(1);
+}
+
+function resolveBinary() {
+  const platformKey = PLATFORM_KEYS[currentPlatform];
+  if (!platformKey) {
+    fail(
+      `unsupported platform ${currentPlatform} — supported: ${Object.keys(PLATFORM_KEYS).join(", ")}`,
+    );
+  }
+  if (typeof packageName !== "string" || packageName === "") {
+    fail("package.json has no package name — reinstall the package");
+  }
+  const platformPackage = `${packageName}-${platformKey}`;
+  try {
+    const manifest = require.resolve(`${platformPackage}/package.json`);
+    const fileName =
+      process.platform === "win32" ? `${BINARY_NAME}.exe` : BINARY_NAME;
+    return path.join(path.dirname(manifest), "bin", fileName);
+  } catch {
+    fail(
+      `installer binary package ${platformPackage} is not installed — it may be missing from the registry or skipped by --no-optional`,
+    );
+  }
+}
+
+const binary = resolveBinary();
+
+const packageRoot = path.join(__dirname, "..");
+const result = spawnSync(
+  binary,
+  ["--package-root", packageRoot, ...process.argv.slice(2)],
+  {
+    stdio: "inherit",
+  },
+);
+
+if (result.error)
+  fail(`could not start the installer (${result.error.message})`);
+if (result.signal) process.kill(process.pid, result.signal);
+process.exit(result.status === null ? 1 : result.status);

package/yaawn/gitignore

@@ -0,0 +1 @@
+yaawn-settings.json

package/yaawn/yaawn-definition-of-done.md

@@ -0,0 +1,5 @@
+# Definition of Done
+
+Standard checklist to verify before considering any work complete.
+
+- [ ] [Clean Code](https://gpcoder.gitbook.io/clean-code)

package/yaawn/yaawn-project-glossary.md

@@ -0,0 +1,7 @@
+# Project Glossary
+
+The project's own settled terms. Technical grilling (`/yaawn-grill-design`) adds each term here the moment it settles, as `- **Term** — definition`, in alphabetical order — terms and short definitions only, no implementation details.
+- **GitHub project** — a GitHub Projects board. Issue templates name the boards their issues are added to in the frontmatter `projects` field.
+- **Issue template** — a markdown template that pre-fills a new issue from its YAML frontmatter. yaawn ships five `yaawn-*` templates.
+- **Language-tagged instruction** — an instruction file named yaawn-<topic>.<language>.instructions.md whose language tag gates installation on the consumer's selected languages.
+- **Projects field** — the `projects` key of an issue template's frontmatter; a list of GitHub project names.

package/yaawn/yaawn-user-roles.md

@@ -0,0 +1,3 @@
+# User Roles
+
+The roles your product's users have — the "As a …" of a user story. The story skills (`/yaawn-prepare-plan`, `/yaawn-write-user-story`, `/yaawn-grill-story`, `/yaawn-split-story`) write stories from these roles. One role per bullet, e.g. `- Account Owner`, optionally followed by ` - ` and a short description of what the role wants to achieve, e.g. `- Account Owner - wants to keep the account secure`. A plain `- Role` bullet with no description still works. With no roles listed, stories are written for the Developer.

package/yaawn/yaawn-verification-commands.md

@@ -0,0 +1,7 @@
+# Verification Commands
+
+Commands `/yaawn-verify-executed-plan` runs from the repo root, in this order. The run stops at the first failure, so list the cheap ones first (lint, typecheck, unit tests) and e2e last. One command per bullet, wrapped in backticks:
+
+- `npm run typecheck`
+- `npm run lint`
+- `npm test`