@jeancodogno/specforce-kit-darwin-arm64 1.0.0-alpha.3 → 1.0.0-beta.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -2,7 +2,7 @@
2
2
  <p align="center">
3
3
  <a href="https://github.com/jeancodogno/specforce-kit/">
4
4
  <picture>
5
- <img src="assets/logo.png" alt="OpenSpec logo" height="128">
5
+ <img src="assets/logo.png" alt="Specforce logo" height="128">
6
6
  </picture>
7
7
  </a>
8
8
  </p>
@@ -73,8 +73,8 @@ The early exploration phase. Use this to brainstorm new features or investigate
73
73
  ### 2. The Constitution (`/spf:constitution`)
74
74
  **Command:** `/spf:constitution {project description}`
75
75
 
76
- The first step in any project. This generates your project's Constitution, containing all rules, principles, UI/UX guidelines, architecture, security, and agent memory.
77
- - **Tool Agnostic & Segmented:** Instead of dumping rules into tool-specific files (like `.clauderc` or `.gemini/GEMINI.md`) or keeping everything in context, Specforce maintains its own specialized, segmented memory files. The agent only loads what it needs. You can switch tools (e.g., from Gemini CLI to Claude Code) and the project memory remains completely intact.
76
+ The first step in any project. This generates your project's Constitution, containing all rules, principles, UI/UX guidelines, architecture, security, and domain module specifications.
77
+ - **Tool Agnostic & Segmented:** Instead of dumping rules into tool-specific files (like `.clauderc` or `.gemini/GEMINI.md`) or keeping everything in context, Specforce maintains its own specialized, segmented specification files. The agent only loads what it needs. You can switch tools (e.g., from Gemini CLI to Claude Code) and the project context remains completely intact.
78
78
  - **Interactive Setup:** Describe your project idea and stack. The agent will ask clarifying questions to help you make foundational decisions.
79
79
  - **Flexible:** Run it once to set up, or rerun it anytime to update the constitution. You can use it on brand new ideas or point it at an existing project to analyze and document its current architecture.
80
80
 
@@ -91,7 +91,7 @@ After you validate the generated spec documents, execute this command. The agent
91
91
  ### 4. Archiving (`/spf:archive`)
92
92
  **Command:** `/spf:archive`
93
93
 
94
- Once implementation is fully complete and verified, this command analyzes what needs to be updated in the project's global Constitution based on the new implementation, and archives the completed spec. It follows standardized **Archiving Instructions** that ensure lessons learned are captured in the project memorial and any project-specific cleanup is performed.
94
+ Once implementation is fully complete and verified, this command synthesizes domain living specifications (`.specforce/docs/modules/`), analyzes what needs to be updated in the project's global Constitution, and archives the completed spec. It follows standardized **Archiving Instructions** that ensure as-built reality is captured into living specs and any project-specific cleanup is performed.
95
95
 
96
96
  ---
97
97
 
package/bin/specforce CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@jeancodogno/specforce-kit-darwin-arm64",
3
- "version": "1.0.0-alpha.3",
3
+ "version": "1.0.0-beta.1",
4
4
  "description": "Native binary for darwin arm64",
5
5
  "license": "MIT",
6
6
  "author": "Jean Codogno <jeancarlo.eng.comp@gmail.com>",