npm - @fro.bot/systematic - Versions diffs - 1.22.8 → 1.23.1 - Mend

@fro.bot/systematic 1.22.8 → 1.23.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (60) hide show

package/commands/ce/brainstorm.md DELETED Viewed

@@ -1,145 +0,0 @@
----
-name: ce:brainstorm
-description: Explore requirements and approaches through collaborative dialogue before planning implementation
-argument-hint: "[feature idea or problem to explore]"
----
-# Brainstorm a Feature or Improvement
-**Note: The current year is 2026.** Use this when dating brainstorm documents.
-Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/ce:plan`, which answers **HOW** to build it.
-**Process knowledge:** Load the `brainstorming` skill for detailed question techniques, approach exploration patterns, and YAGNI principles.
-## Feature Description
-<feature_description> #$ARGUMENTS </feature_description>
-**If the feature description above is empty, ask the user:** "What would you like to explore? Please describe the feature, problem, or improvement you're thinking about."
-Do not proceed until you have a feature description from the user.
-## Execution Flow
-### Phase 0: Assess Requirements Clarity
-Evaluate whether brainstorming is needed based on the feature description.
-**Clear requirements indicators:**
-- Specific acceptance criteria provided
-- Referenced existing patterns to follow
-- Described exact expected behavior
-- Constrained, well-defined scope
-**If requirements are already clear:**
-Use **AskUserQuestion tool** to suggest: "Your requirements seem detailed enough to proceed directly to planning. Should I run `/ce:plan` instead, or would you like to explore the idea further?"
-### Phase 1: Understand the Idea
-#### 1.1 Repository Research (Lightweight)
-Run a quick repo scan to understand existing patterns:
-- task repo-research-analyst("Understand existing patterns related to: <feature_description>")
-Focus on: similar features, established patterns, AGENTS.md guidance.
-#### 1.2 Collaborative Dialogue
-Use the **AskUserQuestion tool** to ask questions **one at a time**.
-**Guidelines (see `brainstorming` skill for detailed techniques):**
-- Prefer multiple choice when natural options exist
-- Start broad (purpose, users) then narrow (constraints, edge cases)
-- Validate assumptions explicitly
-- Ask about success criteria
-**Exit condition:** Continue until the idea is clear OR user says "proceed"
-### Phase 2: Explore Approaches
-Propose **2-3 concrete approaches** based on research and conversation.
-For each approach, provide:
-- Brief description (2-3 sentences)
-- Pros and cons
-- When it's best suited
-Lead with your recommendation and explain why. Apply YAGNI—prefer simpler solutions.
-Use **AskUserQuestion tool** to ask which approach the user prefers.
-### Phase 3: Capture the Design
-Write a brainstorm document to `docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md`.
-**Document structure:** See the `brainstorming` skill for the template format. Key sections: What We're Building, Why This Approach, Key Decisions, Open Questions.
-Ensure `docs/brainstorms/` directory exists before writing.
-**IMPORTANT:** Before proceeding to Phase 4, check if there are any Open Questions listed in the brainstorm document. If there are open questions, YOU MUST ask the user about each one using AskUserQuestion before offering to proceed to planning. Move resolved questions to a "Resolved Questions" section.
-### Phase 4: Handoff
-Use **AskUserQuestion tool** to present next steps:
-**Question:** "Brainstorm captured. What would you like to do next?"
-**Options:**
-1. **Review and refine** - Improve the document through structured self-review
-2. **Proceed to planning** - Run `/ce:plan` (will auto-detect this brainstorm)
-3. **Share to Proof** - Upload to Proof for collaborative review and sharing
-4. **Ask more questions** - I have more questions to clarify before moving on
-5. **Done for now** - Return later
-**If user selects "Share to Proof":**
-```bash
-CONTENT=$(cat docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md)
-TITLE="Brainstorm: <topic title>"
-RESPONSE=$(curl -s -X POST https://www.proofeditor.ai/share/markdown \
-  -H "Content-Type: application/json" \
-  -d "$(jq -n --arg title "$TITLE" --arg markdown "$CONTENT" --arg by "ai:systematic" '{title: $title, markdown: $markdown, by: $by}')")
-PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
-```
-Display the URL prominently: `View & collaborate in Proof: <PROOF_URL>`
-If the curl fails, skip silently. Then return to the Phase 4 options.
-**If user selects "Ask more questions":** YOU (the AI) return to Phase 1.2 (Collaborative Dialogue) and continue asking the USER questions one at a time to further refine the design. The user wants YOU to probe deeper - ask about edge cases, constraints, preferences, or areas not yet explored. Continue until the user is satisfied, then return to Phase 4.
-**If user selects "Review and refine":**
-Load the `document-review` skill and apply it to the brainstorm document.
-When document-review returns "Review complete", present next steps:
-1. **Move to planning** - Continue to `/ce:plan` with this document
-2. **Done for now** - Brainstorming complete. To start planning later: `/ce:plan [document-path]`
-## Output Summary
-When complete, display:
-```
-Brainstorm complete!
-Document: docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md
-Key decisions:
-- [Decision 1]
-- [Decision 2]
-Next: Run `/ce:plan` when ready to implement.
-```
-## Important Guidelines
-- **Stay focused on WHAT, not HOW** - Implementation details belong in the plan
-- **Ask one question at a time** - Don't overwhelm
-- **Apply YAGNI** - Prefer simpler approaches
-- **Keep outputs concise** - 200-300 words per section max
-NEVER CODE! Just explore and document decisions.

package/commands/lfg.md DELETED Viewed

@@ -1,20 +0,0 @@
----
-name: lfg
-description: Full autonomous engineering workflow
-argument-hint: '[feature description]'
-disable-model-invocation: true
----
-Run these slash commands in order. Do not do anything else. Do not stop between steps — complete every step through to the end.
-1. **Optional:** If the `ralph-wiggum` skill is available, run `/ralph-wiggum:ralph-loop "finish all slash commands" --completion-promise "DONE"`. If not available or it fails, skip and continue to step 2 immediately.
-2. `/workflows:plan $ARGUMENTS`
-3. `/systematic:deepen-plan`
-4. `/workflows:work`
-5. `/workflows:review`
-6. `/systematic:resolve_todo_parallel`
-7. `/systematic:test-browser`
-8. `/systematic:feature-video`
-9. Output `<promise>DONE</promise>` when video is in PR
-Start with step 2 now (or step 1 if ralph-wiggum is available).

package/commands/workflows/brainstorm.md DELETED Viewed

@@ -1,145 +0,0 @@
----
-name: workflows:brainstorm
-description: Explore requirements and approaches through collaborative dialogue before planning implementation
-argument-hint: '[feature idea or problem to explore]'
----
-# Brainstorm a Feature or Improvement
-**Note: The current year is 2026.** Use this when dating brainstorm documents.
-Brainstorming helps answer **WHAT** to build through collaborative dialogue. It precedes `/workflows:plan`, which answers **HOW** to build it.
-**Process knowledge:** Load the `brainstorming` skill for detailed question techniques, approach exploration patterns, and YAGNI principles.
-## Feature Description
-<feature_description> #$ARGUMENTS </feature_description>
-**If the feature description above is empty, ask the user:** "What would you like to explore? Please describe the feature, problem, or improvement you're thinking about."
-Do not proceed until you have a feature description from the user.
-## Execution Flow
-### Phase 0: Assess Requirements Clarity
-Evaluate whether brainstorming is needed based on the feature description.
-**Clear requirements indicators:**
-- Specific acceptance criteria provided
-- Referenced existing patterns to follow
-- Described exact expected behavior
-- Constrained, well-defined scope
-**If requirements are already clear:**
-Use **question tool** to suggest: "Your requirements seem detailed enough to proceed directly to planning. Should I run `/workflows:plan` instead, or would you like to explore the idea further?"
-### Phase 1: Understand the Idea
-#### 1.1 Repository Research (Lightweight)
-Run a quick repo scan to understand existing patterns:
-- task repo-research-analyst("Understand existing patterns related to: <feature_description>")
-Focus on: similar features, established patterns, AGENTS.md guidance.
-#### 1.2 Collaborative Dialogue
-Use the **question tool** to ask questions **one at a time**.
-**Guidelines (see `brainstorming` skill for detailed techniques):**
-- Prefer multiple choice when natural options exist
-- Start broad (purpose, users) then narrow (constraints, edge cases)
-- Validate assumptions explicitly
-- Ask about success criteria
-**Exit condition:** Continue until the idea is clear OR user says "proceed"
-### Phase 2: Explore Approaches
-Propose **2-3 concrete approaches** based on research and conversation.
-For each approach, provide:
-- Brief description (2-3 sentences)
-- Pros and cons
-- When it's best suited
-Lead with your recommendation and explain why. Apply YAGNI—prefer simpler solutions.
-Use **question tool** to ask which approach the user prefers.
-### Phase 3: Capture the Design
-Write a brainstorm document to `docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md`.
-**Document structure:** See the `brainstorming` skill for the template format. Key sections: What We're Building, Why This Approach, Key Decisions, Open Questions.
-Ensure `docs/brainstorms/` directory exists before writing.
-**IMPORTANT:** Before proceeding to Phase 4, check if there are any Open Questions listed in the brainstorm document. If there are open questions, YOU MUST ask the user about each one using question before offering to proceed to planning. Move resolved questions to a "Resolved Questions" section.
-### Phase 4: Handoff
-Use **question tool** to present next steps:
-**Question:** "Brainstorm captured. What would you like to do next?"
-**Options:**
-1. **Review and refine** - Improve the document through structured self-review
-2. **Proceed to planning** - Run `/workflows:plan` (will auto-detect this brainstorm)
-3. **Share to Proof** - Upload to Proof for collaborative review and sharing
-4. **Ask more questions** - I have more questions to clarify before moving on
-5. **Done for now** - Return later
-**If user selects "Share to Proof":**
-```bash
-CONTENT=$(cat docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md)
-TITLE="Brainstorm: <topic title>"
-RESPONSE=$(curl -s -X POST https://www.proofeditor.ai/share/markdown \
-  -H "Content-Type: application/json" \
-  -d "$(jq -n --arg title "$TITLE" --arg markdown "$CONTENT" --arg by "ai:compound" '{title: $title, markdown: $markdown, by: $by}')")
-PROOF_URL=$(echo "$RESPONSE" | jq -r '.tokenUrl')
-```
-Display the URL prominently: `View & collaborate in Proof: <PROOF_URL>`
-If the curl fails, skip silently. Then return to the Phase 4 options.
-**If user selects "Ask more questions":** YOU (Claude) return to Phase 1.2 (Collaborative Dialogue) and continue asking the USER questions one at a time to further refine the design. The user wants YOU to probe deeper - ask about edge cases, constraints, preferences, or areas not yet explored. Continue until the user is satisfied, then return to Phase 4.
-**If user selects "Review and refine":**
-Load the `document-review` skill and apply it to the brainstorm document.
-When document-review returns "Review complete", present next steps:
-1. **Move to planning** - Continue to `/workflows:plan` with this document
-2. **Done for now** - Brainstorming complete. To start planning later: `/workflows:plan [document-path]`
-## Output Summary
-When complete, display:
-```
-Brainstorm complete!
-Document: docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md
-Key decisions:
-- [Decision 1]
-- [Decision 2]
-Next: Run `/workflows:plan` when ready to implement.
-```
-## Important Guidelines
-- **Stay focused on WHAT, not HOW** - Implementation details belong in the plan
-- **Ask one question at a time** - Don't overwhelm
-- **Apply YAGNI** - Prefer simpler approaches
-- **Keep outputs concise** - 200-300 words per section max
-NEVER CODE! Just explore and document decisions.

package/skills/brainstorming/SKILL.md DELETED Viewed

@@ -1,190 +0,0 @@
----
-name: brainstorming
-description: This skill should be used before implementing features, building components, or making changes. It guides exploring user intent, approaches, and design decisions before planning. Triggers on "let's brainstorm", "help me think through", "what should we build", "explore approaches", ambiguous feature requests, or when the user's request has multiple valid interpretations that need clarification.
----
-# Brainstorming
-This skill provides detailed process knowledge for effective brainstorming sessions that clarify **WHAT** to build before diving into **HOW** to build it.
-## When to Use This Skill
-Brainstorming is valuable when:
-- Requirements are unclear or ambiguous
-- Multiple approaches could solve the problem
-- Trade-offs need to be explored with the user
-- The user hasn't fully articulated what they want
-- The feature scope needs refinement
-Brainstorming can be skipped when:
-- Requirements are explicit and detailed
-- The user knows exactly what they want
-- The task is a straightforward bug fix or well-defined change
-## Core Process
-### Phase 0: Assess Requirement Clarity
-Before diving into questions, assess whether brainstorming is needed.
-**Signals that requirements are clear:**
-- User provided specific acceptance criteria
-- User referenced existing patterns to follow
-- User described exact behavior expected
-- Scope is constrained and well-defined
-**Signals that brainstorming is needed:**
-- User used vague terms ("make it better", "add something like")
-- Multiple reasonable interpretations exist
-- Trade-offs haven't been discussed
-- User seems unsure about the approach
-If requirements are clear, suggest: "Your requirements seem clear. Consider proceeding directly to planning or implementation."
-### Phase 1: Understand the Idea
-Ask questions **one at a time** to understand the user's intent. Avoid overwhelming with multiple questions.
-**Question Techniques:**
-1. **Prefer multiple choice when natural options exist**
-   - Good: "Should the notification be: (a) email only, (b) in-app only, or (c) both?"
-   - Avoid: "How should users be notified?"
-2. **Start broad, then narrow**
-   - First: What is the core purpose?
-   - Then: Who are the users?
-   - Finally: What constraints exist?
-3. **Validate assumptions explicitly**
-   - "I'm assuming users will be logged in. Is that correct?"
-4. **Ask about success criteria early**
-   - "How will you know this feature is working well?"
-**Key Topics to Explore:**
-| Topic | Example Questions |
-|-------|-------------------|
-| Purpose | What problem does this solve? What's the motivation? |
-| Users | Who uses this? What's their context? |
-| Constraints | Any technical limitations? Timeline? Dependencies? |
-| Success | How will you measure success? What's the happy path? |
-| Edge Cases | What shouldn't happen? Any error states to consider? |
-| Existing Patterns | Are there similar features in the codebase to follow? |
-**Exit Condition:** Continue until the idea is clear OR user says "proceed" or "let's move on"
-### Phase 2: Explore Approaches
-After understanding the idea, propose 2-3 concrete approaches.
-**Structure for Each Approach:**
-```markdown
-### Approach A: [Name]
-[2-3 sentence description]
-**Pros:**
-- [Benefit 1]
-- [Benefit 2]
-**Cons:**
-- [Drawback 1]
-- [Drawback 2]
-**Best when:** [Circumstances where this approach shines]
-```
-**Guidelines:**
-- Lead with a recommendation and explain why
-- Be honest about trade-offs
-- Consider YAGNI—simpler is usually better
-- Reference codebase patterns when relevant
-### Phase 3: Capture the Design
-Summarize key decisions in a structured format.
-**Design Doc Structure:**
-```markdown
----
-date: YYYY-MM-DD
-topic: <kebab-case-topic>
----
-# <Topic Title>
-## What We're Building
-[Concise description—1-2 paragraphs max]
-## Why This Approach
-[Brief explanation of approaches considered and why this one was chosen]
-## Key Decisions
-- [Decision 1]: [Rationale]
-- [Decision 2]: [Rationale]
-## Open Questions
-- [Any unresolved questions for the planning phase]
-## Next Steps
-→ `/workflows:plan` for implementation details
-```
-**Output Location:** `docs/brainstorms/YYYY-MM-DD-<topic>-brainstorm.md`
-### Phase 4: Handoff
-Present clear options for what to do next:
-1. **Proceed to planning** → Run `/workflows:plan`
-2. **Refine further** → Continue exploring the design
-3. **Done for now** → User will return later
-## YAGNI Principles
-During brainstorming, actively resist complexity:
-- **Don't design for hypothetical future requirements**
-- **Choose the simplest approach that solves the stated problem**
-- **Prefer boring, proven patterns over clever solutions**
-- **Ask "Do we really need this?" when complexity emerges**
-- **Defer decisions that don't need to be made now**
-## Incremental Validation
-Keep sections short—200-300 words maximum. After each section of output, pause to validate understanding:
-- "Does this match what you had in mind?"
-- "Any adjustments before we continue?"
-- "Is this the direction you want to go?"
-This prevents wasted effort on misaligned designs.
-## Anti-Patterns to Avoid
-| Anti-Pattern | Better Approach |
-|--------------|-----------------|
-| Asking 5 questions at once | Ask one at a time |
-| Jumping to implementation details | Stay focused on WHAT, not HOW |
-| Proposing overly complex solutions | Start simple, add complexity only if needed |
-| Ignoring existing codebase patterns | Research what exists first |
-| Making assumptions without validating | State assumptions explicitly and confirm |
-| Creating lengthy design documents | Keep it concise—details go in the plan |
-## Integration with Planning
-Brainstorming answers **WHAT** to build:
-- Requirements and acceptance criteria
-- Chosen approach and rationale
-- Key decisions and trade-offs
-Planning answers **HOW** to build it:
-- Implementation steps and file changes
-- Technical details and code patterns
-- Testing strategy and verification
-When brainstorm output exists, `/workflows:plan` should detect it and use it as input, skipping its own idea refinement phase.