I don't think you can get delivered status of change sets associated with a work item using command line.
The following command will list changesets associated with a work item -
>lscm list changesets -W 96704 -r https://localhost:9443/jazz

The following command will list all changesets created by a user
>lscm list changesets -r https://localhost:9443/jazz --creator testJazzUser1

You can add -j option at the end to more details of changesets in jason format which will also include status.
>lscm list changesets -r https://localhost:9443/jazz --creator testJazzUser1 -j

The work items only capture changesets and not the stream/workspace they were flowing to. The status of a changeset can be active or complete. A completed changeset may have been delivered to multiple streams. A changeset does not have delivered state. The delivered status of a changeset is relative to a stream only. If you change the flow target to another stream, all at sudden your change set is not delivered. You can think of 'delivered' more like 'found' and you can use 'locate' command to find a changeset in a workspace or stream. A completed changeset can be found in multiple workspaces or streams and therefore a work item does not tell if a changeset has been delivered.