@atlashub/smartstack-cli 3.39.0 → 3.41.0

package/templates/skills/cc-skill/steps/step-02-generate.md

@@ -1,145 +1,145 @@
----
-name: step-02-generate
-description: Generate SKILL.md file from template based on design choices
-next_step: steps/step-03-steps.md
----
-
-# Step 2: Generate SKILL.md
-
-## MANDATORY EXECUTION RULES:
-- ALWAYS load the appropriate template from `templates/` directory
-- ALWAYS use the design choices from Step 1
-- For UPDATE: read existing SKILL.md first, then apply changes
-- Generate COMPLETE SKILL.md (not a stub)
-
-## YOUR TASK:
-Generate the SKILL.md file based on the skill type and design choices gathered in Step 1.
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Load Template
-
-Based on {skill_type}:
-
-```
-"simple"      → Read: "templates/skill-simple.md"
-"progressive" → Read: "templates/skill-progressive.md"
-"forked"      → Read: "templates/skill-forked.md"
-```
-
-### 2. Create Directory Structure
-
-```bash
-# Create skill directory
-mkdir -p {target_dir}
-
-# For progressive skills, create subdirectories
-mkdir -p {target_dir}/steps/
-mkdir -p {target_dir}/references/  # optional but recommended
-mkdir -p {target_dir}/templates/   # optional, for code templates
-```
-
-### 3. Generate SKILL.md
-
-Use the loaded template as a base. Replace all placeholders with actual values:
-
-**Frontmatter generation:**
-
-```yaml
----
-name: {skill_name}
-description: |
-  {description}
-```
-
-Add optional fields only if they differ from defaults:
-
-```yaml
-# Only if manual-only
-disable-model-invocation: true
-
-# Only if hidden
-user-invocable: false
-
-# Only if skill accepts arguments
-argument-hint: "{argument_hint}"
-
-# Only if not "inherit"
-model: {model}
-
-# Only for forked skills
-context: fork
-agent: {agent}
-allowed-tools: "{allowed_tools}"
-```
-
-Close frontmatter:
-
-```yaml
----
-```
-
-**Content generation:**
-
-Generate appropriate XML sections based on {skill_type}:
-
-**All types get:**
-- `<objective>` - One paragraph from {description}
-- `<quick_start>` - Usage examples with /skill_name
-- `<execution_rules>` - Standard rules
-- `<success_criteria>` - Completion conditions
-
-**Progressive type additionally gets:**
-- `<parameters>` with `<flags>` and `<examples>`
-- `<workflow>` - Numbered high-level steps
-- `<state_variables>` - Table of persistent variables
-- `<entry_point>` - Points to step-00-init.md
-- `<step_files>` - Table mapping steps to files
-
-**Forked type additionally gets:**
-- Note about isolated context
-- Direct workflow (no step loading)
-
-### 4. Write SKILL.md
-
-Use Write tool to create `{target_dir}/SKILL.md` with generated content.
-
-### 5. For UPDATE subcommand
-
-If {subcommand} = "update":
-1. Read existing `{target_dir}/SKILL.md`
-2. Parse current frontmatter and sections
-3. Apply only the requested changes (merge, don't replace entirely)
-4. Use Edit tool to modify specific sections
-5. Preserve any custom content not being updated
-
-### 6. Confirm Generation
-
-```
-Generated: {target_dir}/SKILL.md ({line_count} lines)
-
-Frontmatter:
-  name: {skill_name}
-  description: {description} (truncated)
-  type: {skill_type}
-  ...
-
-Sections: {list of XML sections included}
-
-→ Generating step files...
-```
-
----
-
-## SUCCESS METRICS:
-- SKILL.md created/updated at correct path
-- Frontmatter includes all required fields
-- Appropriate XML sections for skill type
-- Under 500 lines
-- No placeholder text left unreplaced
-
-## NEXT STEP:
-- If {skill_type} = "progressive" → proceed to `./step-03-steps.md`
-- If {skill_type} = "simple" or "forked" → skip to `./step-04-validate.md`
+---
+name: step-02-generate
+description: Generate SKILL.md file from template based on design choices
+next_step: steps/step-03-steps.md
+---
+
+# Step 2: Generate SKILL.md
+
+## MANDATORY EXECUTION RULES:
+- ALWAYS load the appropriate template from `templates/` directory
+- ALWAYS use the design choices from Step 1
+- For UPDATE: read existing SKILL.md first, then apply changes
+- Generate COMPLETE SKILL.md (not a stub)
+
+## YOUR TASK:
+Generate the SKILL.md file based on the skill type and design choices gathered in Step 1.
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. Load Template
+
+Based on {skill_type}:
+
+```
+"simple"      → Read: "templates/skill-simple.md"
+"progressive" → Read: "templates/skill-progressive.md"
+"forked"      → Read: "templates/skill-forked.md"
+```
+
+### 2. Create Directory Structure
+
+```bash
+# Create skill directory
+mkdir -p {target_dir}
+
+# For progressive skills, create subdirectories
+mkdir -p {target_dir}/steps/
+mkdir -p {target_dir}/references/  # optional but recommended
+mkdir -p {target_dir}/templates/   # optional, for code templates
+```
+
+### 3. Generate SKILL.md
+
+Use the loaded template as a base. Replace all placeholders with actual values:
+
+**Frontmatter generation:**
+
+```yaml
+---
+name: {skill_name}
+description: |
+  {description}
+```
+
+Add optional fields only if they differ from defaults:
+
+```yaml
+# Only if manual-only
+disable-model-invocation: true
+
+# Only if hidden
+user-invocable: false
+
+# Only if skill accepts arguments
+argument-hint: "{argument_hint}"
+
+# Only if not "inherit"
+model: {model}
+
+# Only for forked skills
+context: fork
+agent: {agent}
+allowed-tools: "{allowed_tools}"
+```
+
+Close frontmatter:
+
+```yaml
+---
+```
+
+**Content generation:**
+
+Generate appropriate XML sections based on {skill_type}:
+
+**All types get:**
+- `<objective>` - One paragraph from {description}
+- `<quick_start>` - Usage examples with /skill_name
+- `<execution_rules>` - Standard rules
+- `<success_criteria>` - Completion conditions
+
+**Progressive type additionally gets:**
+- `<parameters>` with `<flags>` and `<examples>`
+- `<workflow>` - Numbered high-level steps
+- `<state_variables>` - Table of persistent variables
+- `<entry_point>` - Points to step-00-init.md
+- `<step_files>` - Table mapping steps to files
+
+**Forked type additionally gets:**
+- Note about isolated context
+- Direct workflow (no step loading)
+
+### 4. Write SKILL.md
+
+Use Write tool to create `{target_dir}/SKILL.md` with generated content.
+
+### 5. For UPDATE subcommand
+
+If {subcommand} = "update":
+1. Read existing `{target_dir}/SKILL.md`
+2. Parse current frontmatter and sections
+3. Apply only the requested changes (merge, don't replace entirely)
+4. Use Edit tool to modify specific sections
+5. Preserve any custom content not being updated
+
+### 6. Confirm Generation
+
+```
+Generated: {target_dir}/SKILL.md ({line_count} lines)
+
+Frontmatter:
+  name: {skill_name}
+  description: {description} (truncated)
+  type: {skill_type}
+  ...
+
+Sections: {list of XML sections included}
+
+→ Generating step files...
+```
+
+---
+
+## SUCCESS METRICS:
+- SKILL.md created/updated at correct path
+- Frontmatter includes all required fields
+- Appropriate XML sections for skill type
+- Under 500 lines
+- No placeholder text left unreplaced
+
+## NEXT STEP:
+- If {skill_type} = "progressive" → proceed to `./step-03-steps.md`
+- If {skill_type} = "simple" or "forked" → skip to `./step-04-validate.md`

package/templates/skills/cc-skill/steps/step-03-steps.md

@@ -1,151 +1,151 @@
----
-name: step-03-steps
-description: Generate step files for progressive step loading skills
-next_step: steps/step-04-validate.md
----
-
-# Step 3: Generate Step Files
-
-## MANDATORY EXECUTION RULES:
-- ONLY execute this step for progressive skills ({skill_type} = "progressive")
-- If not progressive, skip directly to step-04-validate.md
-- Generate ALL step files with proper chaining
-- Each step must follow the standard format
-
-## YOUR TASK:
-Generate step files for progressive step loading. Each step file must have proper frontmatter, sections, and next_step chaining.
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Load Step Template
-
-```
-Read: "templates/step-template.md"
-```
-
-### 2. Generate Each Step File
-
-For each step in {steps} array (from Step 1 design):
-
-**File path:** `{target_dir}/steps/step-{number}-{name}.md`
-
-**Frontmatter:**
-
-```yaml
----
-name: step-{number}-{name}
-description: {step_description}
-next_step: steps/step-{next_number}-{next_name}.md
----
-```
-
-For the LAST step: omit `next_step` field.
-
-**Content structure for each step:**
-
-```markdown
-# Step {N}: {Title}
-
-## MANDATORY EXECUTION RULES:
-- [Rules specific to this step]
-- FORBIDDEN to skip to next step until this step is complete
-
-## YOUR TASK:
-{step_description}
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. [First subtask]
-[Instructions for the first subtask]
-
-### 2. [Second subtask]
-[Instructions for the second subtask]
-
-### N. Show Summary
-[Display step results in compact format]
-
----
-
-## SUCCESS METRICS:
-- [What indicates this step succeeded]
-- [Measurable outcomes]
-
-## NEXT STEP:
-After showing summary, proceed directly to `./step-{next_number}-{next_name}.md`
-```
-
-### 3. Special Handling for Step 00 (Init)
-
-The first step (step-00-init) should always include:
-
-```markdown
-## EXECUTION SEQUENCE:
-
-### 1. Parse Input
-Parse flags and arguments from $ARGUMENTS.
-[Include flag parsing based on skill's <parameters>]
-
-### 2. Validate Input
-[Validate required fields, ask user if missing]
-
-### 3. Initialize State
-[Set all state variables to defaults or parsed values]
-
-### 4. Show Summary
-Display compact initialization summary table.
-```
-
-### 4. Special Handling for Last Step
-
-The last step should include:
-
-```markdown
-## EXECUTION SEQUENCE:
-
-### 1. [Final validation or action]
-
-### 2. Final Summary
-Display:
-- What was accomplished
-- Files created/modified
-- Any warnings or next steps
-
-## NEXT STEP:
-This is the final step. Skill execution is complete.
-```
-
-### 5. Write All Step Files
-
-Use Write tool for each step file. Run writes in parallel if possible.
-
-### 6. Confirm Generation
-
-```
-Generated {step_count} step files:
-
-| File | Next Step |
-|------|-----------|
-| steps/step-00-{name}.md | → step-01-{name}.md |
-| steps/step-01-{name}.md | → step-02-{name}.md |
-| ... | ... |
-| steps/step-{N}-{name}.md | (final) |
-
-→ Validating skill...
-```
-
----
-
-## SUCCESS METRICS:
-- All step files created in {target_dir}/steps/
-- Each step has proper frontmatter (name, description, next_step)
-- Step chaining is correct (no broken references)
-- First step handles initialization
-- Last step has completion summary
-- Standard sections present in each step
-
-## NEXT STEP:
-After generating all step files, proceed directly to `./step-04-validate.md`
+---
+name: step-03-steps
+description: Generate step files for progressive step loading skills
+next_step: steps/step-04-validate.md
+---
+
+# Step 3: Generate Step Files
+
+## MANDATORY EXECUTION RULES:
+- ONLY execute this step for progressive skills ({skill_type} = "progressive")
+- If not progressive, skip directly to step-04-validate.md
+- Generate ALL step files with proper chaining
+- Each step must follow the standard format
+
+## YOUR TASK:
+Generate step files for progressive step loading. Each step file must have proper frontmatter, sections, and next_step chaining.
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. Load Step Template
+
+```
+Read: "templates/step-template.md"
+```
+
+### 2. Generate Each Step File
+
+For each step in {steps} array (from Step 1 design):
+
+**File path:** `{target_dir}/steps/step-{number}-{name}.md`
+
+**Frontmatter:**
+
+```yaml
+---
+name: step-{number}-{name}
+description: {step_description}
+next_step: steps/step-{next_number}-{next_name}.md
+---
+```
+
+For the LAST step: omit `next_step` field.
+
+**Content structure for each step:**
+
+```markdown
+# Step {N}: {Title}
+
+## MANDATORY EXECUTION RULES:
+- [Rules specific to this step]
+- FORBIDDEN to skip to next step until this step is complete
+
+## YOUR TASK:
+{step_description}
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. [First subtask]
+[Instructions for the first subtask]
+
+### 2. [Second subtask]
+[Instructions for the second subtask]
+
+### N. Show Summary
+[Display step results in compact format]
+
+---
+
+## SUCCESS METRICS:
+- [What indicates this step succeeded]
+- [Measurable outcomes]
+
+## NEXT STEP:
+After showing summary, proceed directly to `./step-{next_number}-{next_name}.md`
+```
+
+### 3. Special Handling for Step 00 (Init)
+
+The first step (step-00-init) should always include:
+
+```markdown
+## EXECUTION SEQUENCE:
+
+### 1. Parse Input
+Parse flags and arguments from $ARGUMENTS.
+[Include flag parsing based on skill's <parameters>]
+
+### 2. Validate Input
+[Validate required fields, ask user if missing]
+
+### 3. Initialize State
+[Set all state variables to defaults or parsed values]
+
+### 4. Show Summary
+Display compact initialization summary table.
+```
+
+### 4. Special Handling for Last Step
+
+The last step should include:
+
+```markdown
+## EXECUTION SEQUENCE:
+
+### 1. [Final validation or action]
+
+### 2. Final Summary
+Display:
+- What was accomplished
+- Files created/modified
+- Any warnings or next steps
+
+## NEXT STEP:
+This is the final step. Skill execution is complete.
+```
+
+### 5. Write All Step Files
+
+Use Write tool for each step file. Run writes in parallel if possible.
+
+### 6. Confirm Generation
+
+```
+Generated {step_count} step files:
+
+| File | Next Step |
+|------|-----------|
+| steps/step-00-{name}.md | → step-01-{name}.md |
+| steps/step-01-{name}.md | → step-02-{name}.md |
+| ... | ... |
+| steps/step-{N}-{name}.md | (final) |
+
+→ Validating skill...
+```
+
+---
+
+## SUCCESS METRICS:
+- All step files created in {target_dir}/steps/
+- Each step has proper frontmatter (name, description, next_step)
+- Step chaining is correct (no broken references)
+- First step handles initialization
+- Last step has completion summary
+- Standard sections present in each step
+
+## NEXT STEP:
+After generating all step files, proceed directly to `./step-04-validate.md`