function sql-connect( [string] $connStr = "Data Source=PUT_SERVER_HERE; Initial Catalog=PUT_DATABASE_HERE; UID=PUT_USERID_HERE; PWD=PUT_PASSWORD_HERE;" )
{
        $Global:conn = new-Object System.Data.SqlClient.SqlConnection( $connStr )
        $conn.Open()
}

function sql-disconnect()
{
        $conn.Close()
}

function select-sql( [string] $sql )
{
        $cmd = new-Object System.Data.SqlClient.SqlCommand($sql, $conn);
        $rdr = [System.Data.SqlClient.SqlDataReader]$cmd.ExecuteReader();

        $datatable = new-Object System.Data.DataTable
        $datatable.Load($rdr)
        $rdr.Close()

        return $datatable
}

function execute-sql( [string] $sql )
{
        $cmd = new-Object System.Data.SqlClient.SqlCommand($sql, $conn);
        $retval = $cmd.ExecuteNonQuery();

        return $retval
}

I think it comes down to the fact that most good designers are bad implementors. Once designers grasp the concepts, they get really bored with the details. Or they get bogged down with the details initially (pitfall #1). So I can see how speeding through the bare-bones implementation might help.

Maybe better promotion of your game idea will encourage detail-oriented developers to join you? ie. create quick storyboards and notes and publish them.
I dunno -- I'm stuck with lots of ideas and half-finished projects too.

LP