Follow-up from PR #1497 (review thread on .github/prompts/security/sssc-capture.prompt.md).
Context
The Security Planner prompts under .github/prompts/security/ still use the kebab-case agent key in their mode frontmatter (for example mode: security-planner). The dominant codebase convention is the display-name agent key (for example mode: 'Security Planner'), as used by SSSC Planner prompts and most other agent prompts.
Affected files
.github/prompts/security/security-capture.prompt.md.github/prompts/security/security-plan-from-prd.prompt.md
Proposed change
Migrate mode: frontmatter values in the affected prompts from kebab-case agent IDs to the display-name format used elsewhere in the repo, matching the pattern established by SSSC Planner prompts.
Out of scope
This issue is intentionally scoped to the Security Planner prompts. A repo-wide audit of mode key conventions is a separate effort.
Follow-up from PR #1497 (review thread on
.github/prompts/security/sssc-capture.prompt.md).Context
The Security Planner prompts under
.github/prompts/security/still use the kebab-case agent key in theirmodefrontmatter (for examplemode: security-planner). The dominant codebase convention is the display-name agent key (for examplemode: 'Security Planner'), as used by SSSC Planner prompts and most other agent prompts.Affected files
.github/prompts/security/security-capture.prompt.md.github/prompts/security/security-plan-from-prd.prompt.mdProposed change
Migrate
mode:frontmatter values in the affected prompts from kebab-case agent IDs to the display-name format used elsewhere in the repo, matching the pattern established by SSSC Planner prompts.Out of scope
This issue is intentionally scoped to the Security Planner prompts. A repo-wide audit of mode key conventions is a separate effort.