prizmkit 1.1.1 → 1.1.4

package/bundled/team/prizm-dev-team.json

@@ -11,7 +11,7 @@
   "members": [
     {
       "name": "dev",
-      "role": "developer",
+      "role": "developer", 
       "agentDefinition": "prizm-dev-team-dev",
       "prompt": "You are a Dev Agent of the prizm-dev-team. Follow /prizmkit-implement workflow with TDD. Read plan.md/spec.md, implement task-by-task, mark completed tasks [x]. Check .prizm-docs/ TRAPS before implementing.",
       "subscriptions": ["*"]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "prizmkit",
-  "version": "1.1.1",
+  "version": "1.1.4",
   "description": "Create a new PrizmKit-powered project with clean initialization — no framework dev files, just what you need.",
   "type": "module",
   "bin": {

package/src/clean.js

@@ -119,10 +119,10 @@ export async function runClean(directory, options = {}) {
     '.prizm-docs',        // AI-generated project context docs
     'CODEBUDDY.md',
     'CLAUDE.md',
-    'feature-list.json',          // app-planner output
+    'feature-list.json',          // feature-planner output
     'bug-fix-list.json',          // bug-planner output
-    'project-brief.md',           // app-planner project brief
-    'project-conventions.json',   // app-planner coding conventions
+    'project-brief.md',           // feature-planner project brief
+    'project-conventions.json',   // feature-planner coding conventions
     path.join('.codebuddy', 'settings.json'),
     path.join('.claude', 'settings.json'),
     path.join('.claude', 'team-info.json'),

package/src/scaffold.js

@@ -109,7 +109,7 @@ export async function installSkills(platform, skills, projectRoot, dryRun) {
   }
 
   for (const skillName of skills) {
-    // Determine the category subdirectory (prizmkit-skill, prizmkit-tool-skill, orchestration-skill)
+    // Determine the category subdirectory (prizmkit-skill, orchestration-skill)
     const category = skillCategories[skillName];
     if (!category) {
       console.warn(`  ⚠ Skill ${skillName} has no category mapping in metadata, skipping`);
@@ -414,7 +414,7 @@ export async function installSettings(platform, projectRoot, options, dryRun) {
       'Bash(jq *)',
     ];
     if (options.pipeline) {
-      permissions.push('Bash(./dev-pipeline/run.sh *)', 'Bash(./dev-pipeline/launch-daemon.sh *)');
+      permissions.push('Bash(./dev-pipeline/run-feature.sh *)', 'Bash(./dev-pipeline/launch-feature-daemon.sh *)');
     }
 
     const settings = {
@@ -601,8 +601,8 @@ export function resolvePipelineFileList() {
   if (!pipelineSource || !fs.pathExistsSync(pipelineSource)) return [];
 
   const items = [
-    'run.sh', 'retry-feature.sh', 'reset-feature.sh', 'launch-daemon.sh',
-    'run-bugfix.sh', 'retry-bug.sh', 'launch-bugfix-daemon.sh',
+    'run-feature.sh', 'retry-feature.sh', 'reset-feature.sh', 'launch-feature-daemon.sh',
+    'run-bugfix.sh', 'retry-bugfix.sh', 'launch-bugfix-daemon.sh',
     'lib', 'scripts', 'templates', 'assets', 'README.md', '.gitignore',
   ];
 
@@ -638,8 +638,8 @@ export async function installPipeline(projectRoot, dryRun, { forceOverwrite = fa
 
   // 需要安装的 Pipeline 文件和目录
   const items = [
-    'run.sh', 'retry-feature.sh', 'reset-feature.sh', 'launch-daemon.sh',
-    'run-bugfix.sh', 'retry-bug.sh', 'launch-bugfix-daemon.sh',
+    'run-feature.sh', 'retry-feature.sh', 'reset-feature.sh', 'launch-feature-daemon.sh',
+    'run-bugfix.sh', 'retry-bugfix.sh', 'launch-bugfix-daemon.sh',
     'lib', 'scripts', 'templates', 'assets', 'README.md', '.gitignore',
   ];
 

package/bundled/skills/prizmkit-plan/assets/spec-template.md

@@ -1,56 +0,0 @@
-# Feature: [FEATURE_TITLE]
-
-## Overview
-[One paragraph describing the feature purpose and business value]
-
-## User Stories
-
-### US1: [Story Title]
-**As a** [role]
-**I want** [capability]
-**So that** [benefit]
-
-**Acceptance Criteria:**
-- [ ] Given [context], When [action], Then [expected result]
-
-## Scope
-
-### In Scope
-- [Item 1]
-
-### Out of Scope
-- [Item 1]
-
-## Dependencies
-- [Dependency 1]: [Why needed]
-
-## Data Model (if feature involves database changes)
-
-### Existing Schema Reference
-<!-- Read existing schema/model files BEFORE designing new tables. Document observed conventions here. -->
-- Tables reviewed: [list existing tables related to this feature]
-- Naming convention: [snake_case/camelCase — match existing]
-- ID strategy: [UUID/auto-increment — match existing]
-- Timestamp pattern: [created_at/updated_at — match existing]
-- Soft delete: [yes/no, field name — match existing]
-
-### New/Modified Entities
-| Entity | Type (new/modify) | Key Fields | Relationships | Constraints |
-|--------|-------------------|------------|---------------|-------------|
-| [entity_name] | new | [field: type] | [FK to existing_table] | [NOT NULL, UNIQUE, etc.] |
-
-### Open Data Model Questions
-<!-- All questions here MUST be resolved before /prizmkit-plan generates Tasks -->
-- [NEEDS CLARIFICATION] [Any uncertain data model decisions — field types, nullability, relationships]
-
-## Constraints
-- [Constraint 1]
-
-## Clarifications
-[NEEDS CLARIFICATION]: [Ambiguous item]
-
-## Review Checklist
-- [ ] All user stories have acceptance criteria
-- [ ] Scope boundaries are clearly defined
-- [ ] Dependencies are identified
-- [ ] No implementation details (WHAT not HOW)

package/bundled/skills/prizmkit-plan/references/clarify-guide.md

@@ -1,67 +0,0 @@
-# Clarification Phase — Execution Guide
-
-Invoked automatically during `/prizmkit-plan` Phase 0 (specify) when `[NEEDS CLARIFICATION]` markers exist, or during Phase 1 (design) when data model ambiguities arise.
-
----
-
-## Question Strategy
-
-**Ask one question at a time.** Batching questions produces lower-quality answers.
-
-For each question:
-1. Cite the exact location in spec.md (e.g., "§3.2 says...")
-2. State what is ambiguous and why it matters for implementation
-3. Provide a **recommended answer** with rationale — gives the user a concrete starting point to accept, modify, or reject
-
-**Prioritize by implementation impact** (highest first):
-1. Data model (entities, relationships, field types, constraints, naming) — **hardest to change after code is written**
-2. Functional scope boundaries
-3. UX flow and error handling
-4. Non-functional requirements (performance, security)
-5. Edge cases and integration points
-
-## Update Discipline
-
-After **each** user answer:
-- Immediately update `spec.md` (do not batch at the end)
-- Remove the resolved `[NEEDS CLARIFICATION]` marker
-- Re-evaluate for new ambiguities exposed by the answer
-
-## No Limits Policy
-
-**There is no cap on rounds or questions.** Keep asking until:
-- All `[NEEDS CLARIFICATION]` markers are removed, AND
-- No vague or underspecified areas remain, AND
-- You are fully confident about the requirements
-
-If the user's answer raises new questions — ask those too. If a previously-resolved item needs revisiting due to new context — go back.
-
-## Early Termination
-
-If the user says "done", "stop", or "enough" — end immediately and output a summary of:
-- What was resolved
-- What remains unclear (list any open `[NEEDS CLARIFICATION]` items)
-
-## Example Exchange
-
-**Question:**
-> §3.2 says "User can upload files" but doesn't specify file types or size limits.
->
-> **Recommended:** Accept JPEG, PNG, PDF up to 10MB — covers common use cases without straining storage.
->
-> Do you agree, or different constraints?
-
-**User:** "Also allow SVG, make it 25MB"
-
-**Action:** Update spec.md §3.2 → `File upload: JPEG, PNG, PDF, SVG. Max 25MB per file.` Remove marker.
-
-**Follow-up question triggered by answer:**
-> SVGs can contain embedded scripts (XSS risk). Should uploaded SVGs be sanitized (strip `<script>` + event handlers), or restricted to trusted users only?
->
-> **Recommended:** Sanitize all SVG uploads — allows all users to upload safely.
-
-## Guidelines
-
-- Stay at WHAT/WHY level — no implementation details (HOW) in spec
-- If an answer contradicts an existing requirement, surface the conflict and ask which takes precedence
-- If the user seems fatigued: "I have N more questions — continue now or later?" — but never silently stop with unresolved ambiguities