diff --git a/6418c1d923b740057a6138e16664b3c6/description b/6418c1d923b740057a6138e16664b3c6/description
index 63c3ff5..a9ddf25 100644
--- a/6418c1d923b740057a6138e16664b3c6/description
+++ b/6418c1d923b740057a6138e16664b3c6/description
@@ -1,4 +1,4 @@
-add `ent modify ISSUE CHANGE...
+add `ent modify ISSUE CHANGE...`
 
 CHANGE is one or more changes to make to the issue, that looks a bit
 like the FILTER of `ent list`.  Something like:
diff --git a/6418c1d923b740057a6138e16664b3c6/state b/6418c1d923b740057a6138e16664b3c6/state
new file mode 100644
index 0000000..b6fe829
--- /dev/null
+++ b/6418c1d923b740057a6138e16664b3c6/state
@@ -0,0 +1 @@
+backlog
\ No newline at end of file
diff --git a/e43d29638fa3836087794c669cde18a9/description b/e43d29638fa3836087794c669cde18a9/description
new file mode 100644
index 0000000..f32831d
--- /dev/null
+++ b/e43d29638fa3836087794c669cde18a9/description
@@ -0,0 +1,7 @@
+add a Workflow section to the README
+
+This section will describe the typical workflows that ent does well.
+
+This was one thing i found lacking when investigating alternative issue
+tracking systems before starting ent, and i think doing this well could
+help people start using ent.
diff --git a/e43d29638fa3836087794c669cde18a9/state b/e43d29638fa3836087794c669cde18a9/state
new file mode 100644
index 0000000..b6fe829
--- /dev/null
+++ b/e43d29638fa3836087794c669cde18a9/state
@@ -0,0 +1 @@
+backlog
\ No newline at end of file