plan-work

To convert a vague software change request into an actionable plan, supply a plain-language description and optional targets. The skill outputs a narrative plan, a task list, and a context document scoped specifically for agent execution.

The best way to plan an architectural change for an AI agent is to generate a dedicated context document alongside a narrative plan and task list. This scopes boundaries and validation criteria clearly, preventing scope creep during automated execution.

Yes, you can use this approach for roadmap slices, feature requests, and design artifacts. It converts these change types into a scoped execution path with a narrative plan, task list, and context file.

Prevent scope creep by generating a scoped context document that defines clear boundaries and validation criteria alongside the task list. This ensures the agent executes only the planned architectural changes without expanding the project scope.

No, providing specific file targets is optional when creating a software engineering plan. You can supply a plain-language request alone, and the skill will generate the narrative plan, task list, and context file automatically.

Converting a change request generates three markdown artifacts: a narrative plan file, a compact task list file, and a context document file. These are saved under a temporary run-id directory for immediate agent access.