• 0 Posts
  • 2 Comments
Joined 3 years ago
Cake day: July 29th, 2023
  • something183786@lemmy.worldtoProgramming@programming.dev•Looking for advice/experience on spec driven development for a big application while also maintaining an overarching application specEnglish
    4·
    7 days ago

    Superpowers has brainstorming

    Note that the current version injects a lot into the system prompt, and it’s always on. If you using Claude Code, install it in a second profile, so that you choose when to use it. I exploring its features now.

    https://github.com/obra/superpowers

    The Basic Workflow

    1. brainstorming - Activates before writing code. Refines rough ideas through questions, explores alternatives, presents design in sections for validation. Saves design document.

    2. using-git-worktrees - Activates after design approval. Creates isolated workspace on new branch, runs project setup, verifies clean test baseline.

    3. writing-plans - Activates with approved design. Breaks work into bite-sized tasks (2-5 minutes each). Every task has exact file paths, complete code, verification steps.

    4. subagent-driven-development or executing-plans - Activates with plan. Dispatches fresh subagent per task with two-stage review (spec compliance, then code quality), or executes in batches with human checkpoints.

    5. test-driven-development - Activates during implementation. Enforces RED-GREEN-REFACTOR: write failing test, watch it fail, write minimal code, watch it pass, commit. Deletes code written before tests.

    6. requesting-code-review - Activates between tasks. Reviews against plan, reports issues by severity. Critical issues block progress.

    7. finishing-a-development-branch - Activates when tasks complete. Verifies tests, presents options (merge/PR/keep/discard), cleans up worktree.

    The agent checks for relevant skills before any task. Mandatory workflows, not suggestions.

  • something183786@lemmy.worldtoProgramming@programming.dev•I just tried vibe coding with ClaudeEnglish
    7·
    2 months ago

    My preferred way of using LLM coders is:

    • plan only
    • read the spec file I just wrote
    • optionally ask me questions in ‘qa.md’, I’ll reply inline Repeat until it stops asking me questions, then switch to a different model and ask again. I usually use both gpt5.3-codex AND Claude Sonnet

    Then I have it update the spec. I start a new session to have it implement. Finally review the code. If I don’t like it, undo and revisit the spec. Usually it’s because I’m trying to do too much at once. And I need to break it down into multiple specs.