Skip to content

Template should generate numbered Phase 9 structure with duplicate-check on line 1 #9

Closed

Description

@dmccoystephenson

Per the newly-codified conventions in example-skills-catalog/CONVENTIONS.md, the generated Phase 9 should be a numbered structure, not a freeform reflection.

Current generated output

### Phase 9 — Self-audit

Before returning to Phase 1, reflect on the cycle just completed.

Review for any of the following:
- ...

Note any gaps explicitly. File issues in the skill repo (`dmccoystephenson/<slug>-dev-loop`) for human review — do not self-merge changes to the skill.

Proposed template

### Phase 9 — Self-audit

1. **Check for duplicates** before filing:
   \`\`\`bash
   gh issue list --repo dmccoystephenson/<slug>-dev-loop --state open
   \`\`\`

2. **Reflect on the cycle just completed.** Review for any of the following:
   - Instructions that were ambiguous or caused a wrong first attempt
   - Edge cases encountered that are not covered in this skill
   - Project conventions discovered during implementation that the skill should encode
   - Phases that required significantly more or fewer steps than expected

3. **For each gap not already tracked, file an issue:**
   \`\`\`bash
   gh issue create --repo dmccoystephenson/<slug>-dev-loop \
     --title "<short description of the gap>" \
     --body "<what was ambiguous or missing, and suggested instruction text>"
   \`\`\`

4. **Do not implement or merge changes to the skill itself** — file issues only so a human reviews and approves skill edits.

5. If nothing notable is found, note that explicitly and proceed.

This matches example-l-dev-loop and example-q-dev-loop, both of which have this structure. Currently example-h-dev-loop, example-k-dev-loop, kingdom-first-era-dev-loop, and example-a-dev-loop all inherited the unstructured version.


drafted by Claude on behalf of Daniel Stephenson

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions