Skip to content

Idea to Project

Every shipped project starts as a fleeting thought. This guide walks through NeuralRepo’s recommended workflow for taking an idea from initial capture to a completed project.

NeuralRepo uses five statuses that map to natural project phases:

StatusPhaseWhat Happens Here
capturedInboxRaw idea, no evaluation yet. Just get it down.
exploringResearchInvestigate feasibility. Add notes, links, and related ideas.
buildingActive developmentYou are writing code, designing, or creating.
shippedDoneThe project is live, published, or complete.
shelvedOn holdNot abandoned, but not active. Revisit later.
  1. Capture the idea.

    Use whatever method is most convenient — Siri, Claude, CLI, web app, or email. Do not overthink it at this stage. The goal is to not lose the thought.

    Terminal window
    nrepo push "Browser extension that highlights text and saves to NeuralRepo"

    The idea is created with captured status.

  2. Triage and tag.

    Periodically review your captured ideas. Add tags, flesh out the body, and decide whether to explore further or shelve.

    Terminal window
    nrepo tag 42 chrome extension mvp
    nrepo edit 42 --body "Should integrate with the Share Sheet on desktop browsers..."
  3. Move to exploring.

    When you decide to investigate an idea, update its status:

    Terminal window
    nrepo move 42 exploring

    During exploration, research feasibility, check for prior art, and add notes. Use the body field as a living document.

  4. Break it down with relations.

    Large ideas benefit from sub-ideas. Create child ideas for specific components, then link them with a parent relation:

    Terminal window
    nrepo push "Content script for text selection"
    # Then link as child:
    nrepo link 43 42 --type parent
    nrepo push "Popup UI for saving highlighted text"
    nrepo link 44 42 --type parent
    nrepo push "Background service worker for API calls"
    nrepo link 45 42 --type parent

    These appear as children of idea #42, creating a natural work breakdown structure.

  5. Branch for variants.

    If you are considering multiple approaches, use the branch command to create variants:

    Terminal window
    nrepo branch 42 --title "Browser extension — Chrome-only MVP"
    nrepo branch 42 --title "Browser extension — cross-browser with WebExtension API"

    Branches are linked to the original idea with an inspires relation.

  6. Generate an AI spec.

    When you are ready to build, use the develop endpoint to generate a full project specification from your idea and its relations:

    Terminal window
    curl -X POST https://neuralrepo.com/api/v1/ideas/42/develop \
    -H "X-API-Key: nrp_your_key_here"

    This requires a BYOK AI key. The AI reads the idea, its children, and related ideas to produce a structured spec with architecture recommendations, milestones, and open questions.

  7. Pull to your local project.

    Bring the idea and its spec into your working directory:

    Terminal window
    nrepo pull 42 --to ./my-extension

    This creates a markdown file with the full idea context — title, body, tags, related ideas, and the generated spec if available.

  8. Build it.

    Move to building status and start working:

    Terminal window
    nrepo move 42 building

    As you build, update the idea body with progress notes, decisions, and links to the actual code repository.

  9. Ship it.

    When the project is live:

    Terminal window
    nrepo move 42 shipped

    Add a source_url pointing to the live project, repository, or release page.

Beyond status, tags help you track cross-cutting concerns:

  • mvp — minimum viable version of the idea
  • v2 — future improvements after the initial ship
  • blocked — waiting on something external
  • needs-research — requires investigation before building
  • weekend-project — scope fits a weekend
Day 1: nrepo push "Habit tracker with streaks" → captured
Day 3: nrepo move 55 exploring → exploring
Day 3: nrepo tag 55 mobile react-native mvp
Day 5: nrepo push "Streak calculation algorithm"
Day 5: nrepo link 56 55 --type parent
Day 5: nrepo push "Push notification reminders"
Day 5: nrepo link 57 55 --type parent
Day 7: POST /ideas/55/develop → AI spec generated
Day 7: nrepo pull 55 --to ./habit-tracker
Day 8: nrepo move 55 building → building
Day 14: nrepo move 55 shipped → shipped