specrails-core 6.0.0 → 6.1.0

package/templates/kimi/specrails/run-skill.mjs

@@ -231,6 +231,7 @@ export function parseRunnerArgs(argv) {
     attachmentPaths: [],
     extraPrompt: undefined,
     plainPromptStdin: false,
+    renderOnly: false,
   }
   let positionalArgs
   const seenSingleValueFlags = new Set()
@@ -251,8 +252,14 @@ export function parseRunnerArgs(argv) {
       parsed.sessionId = value
       continue
     }
+    if (token === '--render-only') {
+      if (parsed.renderOnly) throw new RunnerUsageError('--render-only may be supplied once')
+      parsed.renderOnly = true
+      continue
+    }
     if (token === PLAIN_PROMPT_STDIN_FLAG) {
-      if (parsed.plainPromptStdin) {
+      if (parsed.renderOnly && parsed.plainPromptStdin) throw new RunnerUsageError('--render-only requires a skill')
+  if (parsed.plainPromptStdin) {
         throw new RunnerUsageError(
           `${PLAIN_PROMPT_STDIN_FLAG} may be supplied once`,
         )
@@ -301,6 +308,7 @@ export function parseRunnerArgs(argv) {
     parsed.rawArgs = positionalArgs
   }
 
+  if (parsed.renderOnly && parsed.plainPromptStdin) throw new RunnerUsageError('--render-only requires a skill')
   if (parsed.plainPromptStdin) {
     for (const flag of ['--skill', '--args', '--prompt', '--attachment']) {
       if (
@@ -594,6 +602,12 @@ export async function runSkillCli(argv, dependencies = {}) {
   }
   const scriptPath = dependencies.scriptPath ?? process.argv[1]
   const providerRoot = resolveProviderRoot(scriptPath)
+  if (parsedArgs.renderOnly) {
+    const { prompt } = prepareSkillLaunch({ ...parsedArgs, providerRoot }, dependencies)
+    assertManagedPrompt(prompt)
+    ;(dependencies.writeStdout ?? (text => process.stdout.write(text)))(JSON.stringify({ prompt }) + '\n')
+    return 0
+  }
   if (parsedArgs.plainPromptStdin) {
     const readStdin =
       dependencies.readStdin ??

package/templates/commands/specrails/batch-implement.md

@@ -1,32 +0,0 @@
-# Programmatic implementation
-
-Implement the requested spec or batch through the installed agent runtime. The runtime owns architecture, development, verification, review and archive; do not delegate these phases yourself or launch a second coordinator.
-
-## Freeze the requested scope
-
-Use the supplied absolute `SPECRAILS_EXECUTION_CONTEXT` unchanged. It defines runId, specs and acceptance criteria, artifactRoot, selected repositories and ownership. For standalone use, admit the exact requested tickets once with:
-
-```sh
-node .specrails/runtime/pipeline.mjs init --change <stable-change> --tickets "<requested-ids>"
-```
-
-For a free-form request use `--scope-request <absolute-json>` with the user's specs and criteria. Use the returned absolute context path. Never select a different run by modification time or replace scope from mutable backlog. Multiple tickets share one aggregate context and one runtime invocation.
-
-## Execute
-
-```sh
-node .specrails/runtime/agent-runtime.mjs run --context <absolute-context> --config .specrails/agent-runtime.json --change <stable-change>
-```
-
-Desktop launches this runtime directly and freezes its resolved global connections and project settings. Standalone installations provide a local configuration. If required runtime/configuration files are missing, repair the Core installation; do not fall back to a prompt-orchestrated implementation.
-
-Wait for the foreground process. Report its structured status, acceptance and verification evidence. A process failure or pause preserves progress; it does not authorize a replacement run. Resume only the exact saved execution:
-
-```sh
-node .specrails/runtime/agent-runtime.mjs status --context <absolute-context>
-node .specrails/runtime/agent-runtime.mjs resume --context <absolute-context>
-```
-
-Answers, approvals and recovery flags must correspond to the pending request and user authorization. Resume keeps the saved models, scope and configuration. Never manually rewrite phase receipts, bypass review, or treat provider prose as completion.
-
-Honor the context's ownership throughout: Desktop owns worktrees, commits, PRs and backlog delivery. Runtime success prepares a reviewed candidate; host delivery remains a separate action. Preview requests must not invoke mutating execution.