@liangxie/qf 0.0.1

package/openspec/changes/archive/2026-07-03-add-say-command/specs/cli-framework/spec.md

@@ -0,0 +1,22 @@
+## ADDED Requirements
+
+### Requirement: CLI entry point
+The system SHALL have a main entry point file (`index.js`) that initializes the CLI framework.
+
+#### Scenario: CLI initializes successfully
+- **WHEN** user runs `qf` command
+- **THEN** system displays help information or version
+
+### Requirement: Command registration
+The system SHALL support registering commands using commander library.
+
+#### Scenario: Command is registered
+- **WHEN** developer defines a command in index.js
+- **THEN** command is available via `qf <command-name>`
+
+### Requirement: Package configuration
+The system SHALL have proper npm package configuration for CLI usage.
+
+#### Scenario: Package has bin field
+- **WHEN** developer runs `npm link`
+- **THEN** `qf` command is available globally

package/openspec/changes/archive/2026-07-03-add-say-command/specs/say-command/spec.md

@@ -0,0 +1,22 @@
+## ADDED Requirements
+
+### Requirement: Say command exists
+The system SHALL have a `say` command that can be invoked via `qf say`.
+
+#### Scenario: Say command is available
+- **WHEN** user runs `qf say`
+- **THEN** command executes without error
+
+### Requirement: Say command outputs hello
+The system SHALL output "hello" when the `say` command is executed.
+
+#### Scenario: Say command outputs hello
+- **WHEN** user runs `qf say`
+- **THEN** system outputs "hello" to stdout
+
+### Requirement: Say command has no arguments
+The system SHALL NOT accept any arguments for the `say` command.
+
+#### Scenario: Say command ignores arguments
+- **WHEN** user runs `qf say world`
+- **THEN** system still outputs "hello" (ignoring "world")

package/openspec/changes/archive/2026-07-03-add-say-command/tasks.md

@@ -0,0 +1,17 @@
+## 1. Setup
+
+- [x] 1.1 Create `index.js` file with shebang line
+- [x] 1.2 Add commander dependency to package.json
+- [x] 1.3 Add bin field to package.json
+
+## 2. Core Implementation
+
+- [x] 2.1 Import commander in index.js
+- [x] 2.2 Define `say` command that outputs "hello"
+- [x] 2.3 Configure program name and version
+
+## 3. Testing
+
+- [x] 3.1 Run `npm link` to test locally
+- [x] 3.2 Test `qf say` command outputs "hello"
+- [x] 3.3 Verify command works with arguments (should ignore them)

package/openspec/config.yaml

@@ -0,0 +1,20 @@
+schema: spec-driven
+
+# Project context (optional)
+# This is shown to AI when creating artifacts.
+# Add your tech stack, conventions, style guides, domain knowledge, etc.
+# Example:
+#   context: |
+#     Tech stack: TypeScript, React, Node.js
+#     We use conventional commits
+#     Domain: e-commerce platform
+
+# Per-artifact rules (optional)
+# Add custom rules for specific artifacts.
+# Example:
+#   rules:
+#     proposal:
+#       - Keep proposals under 500 words
+#       - Always include a "Non-goals" section
+#     tasks:
+#       - Break tasks into chunks of max 2 hours

package/package.json

@@ -0,0 +1,25 @@
+{
+  "name": "@liangxie/qf",
+  "version": "0.0.1",
+  "description": "cli for qframework",
+  "keywords": [
+    "qframework",
+    "gamedevelopment",
+    "systemdesign",
+    "unity",
+    "godot"
+  ],
+  "license": "ISC",
+  "author": "liangxie",
+  "type": "commonjs",
+  "main": "index.js",
+  "bin": {
+    "qf": "./index.js"
+  },
+  "scripts": {
+    "test": "echo \"Error: no test specified\" && exit 1"
+  },
+  "dependencies": {
+    "commander": "^12.0.0"
+  }
+}