← Back to context

Comment by rahimnathwani

1 month ago

When GPT-4.5 came out, I used it to write a couple of novels for my son. I had some free API credits, and used a naive workflow:

while word_count < x: write_next_chapter(outline, summary_so_far, previous_chapter_text)

It worked well enough that the novels were better than the median novel aimed at my son's age group, but I'm pretty sure we can do better.

There are web-based tools to help fiction authors to keep their stories straight: they use some data structures to store details about the world, the characters, the plot, the subplots etc., and how they change during each chapter.

I am trying to make an agent skill that has two parts:

- the SKILL.md that defines the goal (what criteria the novel must satisfy to be complete and good) and the general method

- some other md files that describe different roles (planner, author, editor, lore keeper, plot consistency checker etc.)

- a python file which the agent uses as the interface into the data structure (I want it to have a strong structure, and I don't like the idea of the agent just editing a bunch of json files directly)

For the first few iterations, I'm using cheap models (Gemini Flash ones) to generate the stories, and Opus 4.6 to provide feedback. Once I think the skill is described sufficiently well, I'll use a more powerful model for generation and read the resulting novel myself.

this is fascinating. I would like to try this as a side project as well.

some other md files that describe different roles (planner, author, editor, lore keeper, plot consistency checker etc.)

- What are these meant to be exactly? are these sub agents in the workflow or am i completely misunderstanding?

  • "are these sub agents in the workflow"

    The idea is that on any 'turn', the AI model should be doing only one of those tasks. That's true whether it's in the main thread (with all the past context) or has just been launched as a subagent.

    You can see an example of this pattern here in Anthropic's skills repo: https://github.com/anthropics/skills/tree/main/skills/skill-... (the repo has four separate skill.md files: a main SKILLS.md and then three others for specialist roles)

    Whether they're run as subagents (a separate AI chat session with clean context) is a separate decision, and it depends on whether the coding harness supports that. https://agentskills.io/client-implementation/adding-skills-s...

    I'm still trying to figure out the subagent delegation stuff.