What problem does this solve?
When reviewing design, it helps to know how many sections there are instead of just presenting them one-by-one. Reading a summary of upcoming design sections will also help me to think ahead about what my answer would be, and give me an idea of what kinds of questions the skill has.
Proposed solution
I just want the skill to present a list of design sections before asking about them. Could be in ASCII table format, or just a list with an index counter and a one-line description.
Changing "Section 1: section_description" to "Section 1 of N: section_description" would be useful so I know how many sections are left.
What alternatives did you consider?
I usually inject a prompt between sections (after the third or fourth one) and ask how many sections are left.
Is this appropriate for core Superpowers?
Yes.
Context
N/A
What problem does this solve?
When reviewing design, it helps to know how many sections there are instead of just presenting them one-by-one. Reading a summary of upcoming design sections will also help me to think ahead about what my answer would be, and give me an idea of what kinds of questions the skill has.
Proposed solution
I just want the skill to present a list of design sections before asking about them. Could be in ASCII table format, or just a list with an index counter and a one-line description.
Changing "Section 1: section_description" to "Section 1 of N: section_description" would be useful so I know how many sections are left.
What alternatives did you consider?
I usually inject a prompt between sections (after the third or fourth one) and ask how many sections are left.
Is this appropriate for core Superpowers?
Yes.
Context
N/A