schub 0.1.25 → 0.1.26

package/skills/review-proposal/SKILL.md

@@ -1,40 +0,0 @@
----
-name: review-proposal
-description: "Run a review session for a proposal by creating a list of open questions, updating the proposal, adding a Q&A section, and deleting REVIEW_ME.md on completion. Use when asked to review proposals."
----
-
-## User Input (proposal-id or shorthand `P####`)
-
-```text
-$ARGUMENTS
-```
-
-## Workflow
-
-1. Load the proposal files locally (they may not exist yet):
-   - Run `npx schub proposals pull --proposal-id "<shorthand>"`.
-2. Confirm `.schub/proposals/<proposal-id>/proposal.md` exists. If it is missing, ask the user to run the create-proposal skill first. If it is still a draft, ask the user to review it first.
-3. Review the proposal by checking the [MISSING INFORMATION] tags and the potential issues listed.
-4. If there are issues, or missing information, run `npx schub templates create --name "review" --proposal-id "<proposal-id>"` to scaffold `.schub/proposals/<proposal-id>/REVIEW_ME.md`.
-5. Triage each item:
-   - **High-stakes** (scope, risks, dependencies, security, performance): create a bullet point item in the review checklist.
-   - **Minute details** (naming, copy, formatting, low-impact defaults): make a decision update the proposal and mark as an assumption in the proposal.
-6. Once the review checklist is completed, gather unchecked items (`- [ ]`) in order.
-7. Start the review loop (process unchecked items in order), ask each item as a question. If unclear, ask a quick follow-up and do not advance.
-   - Update the review checklist accordingly inline with the answers.
-8. When no unchecked items remain, update the plan with the new information.
-9. When no unchecked items remain, run `npx schub review complete --proposal-id "<proposal-id>"` to create `.schub/proposals/<proposal-id>/Q&A.md`.
-   - Ask the LLM to migrate the TODO block into the Q&A sections and remove the TODO block.
-10. Mark the proposal Status as "Accepted".
-
-## Output Locations
-
-- Proposal: `.schub/proposals/<proposal-id>/proposal.md`
-- (OPTIONAL) Review In Progress: `.schub/proposals/<proposal-id>/REVIEW_ME.md`
-- (OPTIONAL) Review Completed: `.schub/proposals/<proposal-id>/Q&A.md`
-
-## Notes
-
-- Avoid expanding scope beyond missing information in the proposal.
-- Focus review on high-stakes issues; place details into assumptions instead of asking.
-- **Do not start the implementation** only edit the `proposals` folder.

package/templates/create-tasks/task-template.md

@@ -1,69 +0,0 @@
----
-proposal_id: "{{PROPOSAL_ID}}"
-priority: "[P1|P2|P3]"
-depends_on: []
-parallelizable: "[no|yes]"
-blocked_reason: ""
----
-
-# Ticket: {{TICKET_ID}} {{TICKET_TITLE}}
-
-## Goal
-
-[What this ticket accomplishes, in one paragraph.]
-
-## Cookbook References
-
-[Link to relevant cookbook sections when available. If none exist, state that and capture gaps in Implementation Notes.]
-
-- [Cookbook section link or note]
-
-## Scope
-
-### In Scope
-
-- [Included work]
-- [Tests required to validate work (or explicitly "none")]
-- [Documentation updates required or explicitly none]
-
-### Out of Scope
-
-- [Explicitly excluded work]
-
-## Implementation Notes
-
-[Describe the approach, key files/modules, assumptions, and include code snippets.]
-
-- [Key files/modules to touch]
-- [Assumptions or gaps from cookbook references]
-
-```ts
-[Insert relevant planned code changes.]
-```
-
-## Documentation
-
-[Describe documentation updates required or state "No documentation updates required."]
-
-## Steps
-
-- [ ] Red — [Add/expand tests in `path/to/test` for specific cases.]
-- [ ] Green — [Implement minimal code to satisfy the tests.]
-- [ ] Refactor — [Simplify, remove legacy code, improve structure.]
-- [ ] Docs — [Update docs if needed.]
-- [ ] Validation — [Run required commands and capture artifacts.]
-
-## Acceptance
-
-[Each acceptance item should map to the explicit tests or commands below. Documentation is validated by review and does not require tests.]
-
-- [ ] [Outcome 1 Pass condition: clearly state what must be true]
-- [ ] [Outcome 2 Pass condition: clearly state what must be true]
-- [ ] [Outcome 3 Pass condition: clearly state what must be true]
-- ...
-
-## Evidence
-
-[Point to artifacts under `.schub/artifacts/<ticket-id>/`. The artifacts must include a way to recreate the outputs (e.g. commands used).]
-
-- [build outputs, e2e artifacts, test outputs, screenshots, traces, curl responses]