Smarter README

Author: dannyob

README.md

@@ -1,2 +1,7 @@
 # spec-u-llm
-Using LLMs to Improve the Filecoin Spec
+
+Using LLMs to update the [Filecoin specification](https://spec.filecoin.io/). A
+Fast Phil experiment from the [2024 Chiang Mai Filecoin Hacker
+House](https://filecoin.notion.site/Filecoin-Hacker-House-Runbook-10a7631f282580dcb872d18bac5959ee).
+
+

prompts/list_changes_in_FIP.md

@@ -2,12 +2,33 @@ You are an expert in writing and editing specifications, and knowledge about
 blockchains, cryptoeconomics, cryptographic proofs and the Filecoin ecosystem
 in particular.
 
-I've included the full Filecoin specification, and a proposed FIP which may
-require changing the specification if its change is accepted.
+I've included the full Filecoin specification as a set of markdown files, and
+the text of a FIP (Filecoin Improvement Proposal) which may require making changes
+to the specification. 
+
+The FIP has been accepted, and now we have to plan to update the specification.
 
 Identify and summarise in a numbered list the changes to the specification
 document made by the FIP, with the names of relevant specification files that
 will need to be modified. Err on the side of including relevant specification
 files in the list.
 
-If no obvious changes are proposed in the FIP, say "0. No changes made."
+
+Use this format:
+
+```markdown
+# SPEC CHANGES
+## CHANGE #1
+A description of the change.
+### Specification files affected
+content/algorithms/block_sync.md
+../specs/content/systems/filecoin_markets/retrieval_market/retrieval_peer_resolver.md
+
+### CHANGE #2
+Another description of another change.
+### Specification files affected
+../specs/content/glossary/_index.md
+../specs/content/intro/filecoin_vm.md
+```
+
+If no obvious changes are proposed in the FIP, say "# NO CHANGES NECESSARY FOR FIP".