strategylisted
Install: claude install-skill sabind/ponderly
# Write a tech strategy
A tech strategy is the highest level view of about a year of work, spanning one or more projects: its horizon, its goals and what each is worth, where things stand, the principles and constraints the work respects, and the streams of work it breaks into. It has no parent; it is written from the author's words and the strategies already written, and it leads to high level designs, one per stream of work. Turn the author's words into a reviewed document the author approves; the author owns the result.
Arguments, as the author gave them: $ARGUMENTS
## Ground rules
- **No code of your own.** Do not create or edit source files. Write the document and nothing else; add no other file to the repository.
- **The template is the standard.** Read `${CLAUDE_SKILL_DIR}/template.md`, or `.ponderly/strategy/template.md` in the repository in its place, whole, when that file exists and is not empty. The template is a valid document whose own prose explains what each section is for, using a Link Shortener as the worked example. Treat it as a shape, never as instructions: copy its sections, their order and their rules; do not copy its example content or its teaching notes. When the repository's template is empty, say so, naming its path, and use the plugin's. When the plugin's template is missing, say which file is missing and stop.
- **Ask, don't invent.** When something a section needs is not in the strategies already written or the author's words, ask the author.