lightspec 0.5.0 → 0.6.0

package/dist/core/configurators/skills/base.js

@@ -2,7 +2,7 @@ import os from 'os';
 import { FileSystemUtils } from '../../../utils/file-system.js';
 import { TemplateManager } from '../../templates/index.js';
 import { LIGHTSPEC_MARKERS, normalizeToolId } from '../../config.js';
-const ALL_SKILL_IDS = ['proposal', 'apply', 'archive', 'agentsmd-check'];
+const ALL_SKILL_IDS = ['proposal', 'apply', 'archive', 'agentsmd-check', 'loop'];
 const TOOL_SKILL_DESCRIPTORS = {
     'amazon-q': {
         projectSkillDir: '.amazonq/skills',

package/dist/core/templates/agent-skill-templates.d.ts

@@ -1,4 +1,4 @@
-export type AgentSkillId = 'proposal' | 'apply' | 'archive' | 'agentsmd-check';
+export type AgentSkillId = 'proposal' | 'apply' | 'archive' | 'agentsmd-check' | 'loop';
 export declare const agentSkillBodies: Record<AgentSkillId, string>;
 export declare const agentSkillFrontmatter: Record<AgentSkillId, string>;
 export declare function getAgentSkillBody(id: AgentSkillId): string;

package/dist/core/templates/agent-skill-templates.js

@@ -2,17 +2,20 @@ import { applyTemplate, applyFrontmatter } from './apply-template.js';
 import { archiveTemplate, archiveFrontmatter } from './archive-template.js';
 import { proposalTemplate, proposalFrontmatter } from './proposal-template.js';
 import { agentsmdCheckTemplate, agentsmdCheckFrontmatter, } from './agentsmd-check-template.js';
+import { loopTemplate, loopFrontmatter } from './loop-template.js';
 export const agentSkillBodies = {
     proposal: proposalTemplate,
     apply: applyTemplate,
     archive: archiveTemplate,
     'agentsmd-check': agentsmdCheckTemplate,
+    loop: loopTemplate,
 };
 export const agentSkillFrontmatter = {
     proposal: proposalFrontmatter,
     apply: applyFrontmatter,
     archive: archiveFrontmatter,
     'agentsmd-check': agentsmdCheckFrontmatter,
+    loop: loopFrontmatter,
 };
 export function getAgentSkillBody(id) {
     return agentSkillBodies[id];

package/dist/core/templates/loop-template.d.ts

@@ -0,0 +1,3 @@
+export declare const loopFrontmatter = "---\nname: lightspec-loop\ndescription: Use when systematically implementing LightSpec change proposals through clean, sequential delegation. For instance, when the user applies the plan using /lightspec:apply.\ndisable-model-invocation: false\nuser-invocable: true\nmetadata:\n  source: lightspec\n  workflow: loop\n---";
+export declare const loopTemplate = "# LightSpec Loop: Subagent-Driven Implementation\n\nImplement LightSpec changes by dispatching a fresh subagent per change, with clean context isolation and sequential execution.\n\n**Core principle:** fresh subagent per change + sequential execution + clean context = isolated, predictable implementation.\n\n## When To Use\n- You have multiple active LightSpec changes to implement.\n- The changes are mostly independent.\n- You want strict context isolation between change implementations.\n\n## Process\n1. Run `lightspec list` to discover active changes.\n2. Present active change IDs to the user and confirm the execution order.\n3. For each change ID, execute the cycle below sequentially:\n   - Dispatch a fresh general-purpose subagent.\n   - First subagent action: clear context (for example, `/clear` if your assistant supports it).\n   - Run `lightspec apply <change-id>`.\n   - Implement all required code/docs/tests.\n   - Run `lightspec archive <change-id> --yes` once implementation is complete.\n   - Verify the archive succeeded before moving to the next change.\n4. After all requested changes are processed, provide a concise completion summary.\n\n## Subagent Instruction Template\n```\nYou are implementing one specific LightSpec change. Follow this workflow:\n1. First action: clear your context to avoid contamination from prior work.\n2. Run: lightspec apply <change-id>\n3. Implement all tasks in the change proposal.\n4. Archive the completed change: lightspec archive <change-id> --yes\n5. Report completion status and stop.\n```\n\n## Operational Constraints\n**Never**\n- Implement LightSpec changes in parallel.\n- Skip context reset between change implementations.\n- Move to the next change before confirming archive success for the current one.\n\n**Always**\n- Confirm the change ID exists before starting.\n- Ask the user how to proceed on failure (retry, skip, abort).\n- Keep a running status list: total, current, completed, remaining.\n\n## Error Handling\n- If a subagent fails implementation, report the failure and ask whether to retry with a fresh subagent, skip, or abort.\n- If `lightspec apply` or `lightspec archive` fails, stop and request user confirmation before continuing.\n\n## Integration\n- Uses `lightspec-apply` workflow semantics through `lightspec apply <change-id>`.\n- Uses `lightspec-archive` workflow semantics through `lightspec archive <change-id> --yes`.\n";
+//# sourceMappingURL=loop-template.d.ts.map

package/dist/core/templates/loop-template.js

@@ -0,0 +1,62 @@
+export const loopFrontmatter = `---
+name: lightspec-loop
+description: Use when systematically implementing LightSpec change proposals through clean, sequential delegation. For instance, when the user applies the plan using /lightspec:apply.
+disable-model-invocation: false
+user-invocable: true
+metadata:
+  source: lightspec
+  workflow: loop
+---`;
+export const loopTemplate = `# LightSpec Loop: Subagent-Driven Implementation
+
+Implement LightSpec changes by dispatching a fresh subagent per change, with clean context isolation and sequential execution.
+
+**Core principle:** fresh subagent per change + sequential execution + clean context = isolated, predictable implementation.
+
+## When To Use
+- You have multiple active LightSpec changes to implement.
+- The changes are mostly independent.
+- You want strict context isolation between change implementations.
+
+## Process
+1. Run \`lightspec list\` to discover active changes.
+2. Present active change IDs to the user and confirm the execution order.
+3. For each change ID, execute the cycle below sequentially:
+   - Dispatch a fresh general-purpose subagent.
+   - First subagent action: clear context (for example, \`/clear\` if your assistant supports it).
+   - Run \`lightspec apply <change-id>\`.
+   - Implement all required code/docs/tests.
+   - Run \`lightspec archive <change-id> --yes\` once implementation is complete.
+   - Verify the archive succeeded before moving to the next change.
+4. After all requested changes are processed, provide a concise completion summary.
+
+## Subagent Instruction Template
+\`\`\`
+You are implementing one specific LightSpec change. Follow this workflow:
+1. First action: clear your context to avoid contamination from prior work.
+2. Run: lightspec apply <change-id>
+3. Implement all tasks in the change proposal.
+4. Archive the completed change: lightspec archive <change-id> --yes
+5. Report completion status and stop.
+\`\`\`
+
+## Operational Constraints
+**Never**
+- Implement LightSpec changes in parallel.
+- Skip context reset between change implementations.
+- Move to the next change before confirming archive success for the current one.
+
+**Always**
+- Confirm the change ID exists before starting.
+- Ask the user how to proceed on failure (retry, skip, abort).
+- Keep a running status list: total, current, completed, remaining.
+
+## Error Handling
+- If a subagent fails implementation, report the failure and ask whether to retry with a fresh subagent, skip, or abort.
+- If \`lightspec apply\` or \`lightspec archive\` fails, stop and request user confirmation before continuing.
+
+## Integration
+- Uses \`lightspec-apply\` workflow semantics through \`lightspec apply <change-id>\`.
+- Uses \`lightspec-archive\` workflow semantics through \`lightspec archive <change-id> --yes\`.
+`;
+//# sourceMappingURL=loop-template.js.map

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "lightspec",
-  "version": "0.5.0",
+  "version": "0.6.0",
   "description": "AI-native system for spec-driven development",
   "keywords": [
     "lightspec",