@snappedly-tools/shipyard 0.5.0 → 0.6.0

package/dist/templates/simple-loop/prompt.md

@@ -1,53 +1,19 @@
-# Context
+# Assigned issue scope
 
-## Open issues
+Implement scope #{{TASK_ID}} ({{ISSUE_TITLE}}) on branch `{{BRANCH}}`.
+Read it with `gh issue view {{TASK_ID}} --comments`, including acceptance criteria, and read `AGENTS.md`, `CONTEXT.md`, `docs/agents/workflow.md`, and relevant ADRs. The selector resolved the selected tickets and their dependencies below.
 
-!`{{LIST_TASKS_COMMAND}}`
+Follow {{SKILL}} for this scope. For a planning spec, deliver only tickets in `SCOPE.tickets` in dependency order on this one branch. Other linked tickets are context; do not implement them. Integrate, clean up, and review the selected work before handoff. Child workers may follow `/implement` under `/implement-spec` coordination. Do not create separate child PRs. Use `/tdd` for changed logic, then `/code-cleanup` and `/code-review` as the skill and repository policy require. Run candidate dependency installation again after changing manifests: `bash .shipyard/setup.sh`. Complete the required checks, resolve review findings, and commit all task work. Do not close the issue, merge into the target branch, or publish the PR; the surrounding workflow handles handoff.
 
-The list above has already been filtered to issues ready for work and is the sole source of truth for what work exists. Do not run your own unfiltered query to find more issues — if the list is empty, there is nothing to do.
+If requirements, checks, or review are unresolved, describe the blocker and stop without the completion marker. Only after the verified commit, finish with a concise evidence packet containing changed scope, `Checks: <commands and results>`, `Review: APPROVED`, and limitations:
 
-## Recent RALPH commits (last 10)
-
-!`git log --oneline --grep="RALPH" -10`
-
-# Task
-
-You are RALPH — an autonomous coding agent working through issues one at a time.
-
-## Priority order
-
-Work on issues in this order:
-
-1. **Bug fixes** — broken behaviour affecting users
-2. **Tracer bullets** — thin end-to-end slices that prove an approach works
-3. **Polish** — improving existing functionality (error messages, UX, docs)
-4. **Refactors** — internal cleanups with no user-visible change
-
-Pick the highest-priority open issue that is not blocked by another open issue.
-
-## Workflow
-
-1. **Explore** — read the issue carefully. Pull in the parent PRD if referenced. Read the relevant source files and tests before writing any code.
-2. **Plan** — decide what to change and why. Keep the change as small as possible.
-3. **Execute** — use RGR (Red → Green → Repeat → Refactor): write a failing test first, then write the implementation to pass it.
-4. **Verify** — read the repository's configured feedback-loop contract and run every applicable check for this change. Use the configured static check and focused behavior tests when they exist; include formatting, build, or broader checks when the contract or change requires them. Fix failures before proceeding.
-5. **Commit** — make a single git commit. The message MUST:
-   - Start with `RALPH:` prefix
-   - Include the task completed and any PRD reference
-   - List key decisions made
-   - List files changed
-   - Note any blockers for the next iteration
-6. **Close** — close the issue with `{{CLOSE_TASK_COMMAND}}` explaining what was done.
-
-## Rules
-
-- Work on **one issue per iteration**. Do not attempt multiple issues in a single iteration.
-- Do not close an issue until you have committed the fix and verified tests pass.
-- Do not leave commented-out code or TODO comments in committed code.
-- If you are blocked (missing context, failing tests you cannot fix, external dependency), leave a comment on the issue and move on — do not close it.
+<handoff>...</handoff>
+<promise>COMPLETE</promise>
 
-# Done
+## Resolved scope
 
-When all actionable issues are complete (or you are blocked on all remaining ones), or the open-issues block at the top of this prompt is empty, output the completion signal:
+```json
+{{SCOPE}}
+```
 
-<promise>COMPLETE</promise>
+Read the complete parent and child issue bodies and comments with `gh issue view`, including repository guidance and dependency links.