Enhance GitHub issue creation workflow with procedures and templates

## Problem Statement

When users ask "create a GitHub issue for xyz", the current workflow doesn't automatically incorporate:
- Existing procedures that might be relevant
- GitHub issue templates that provide structure
- Contextual guidance based on issue type

## Proposed Solution

Create procedures that enhance the GitHub issue creation workflow to:

1. **Auto-detect issue type** from user request and suggest appropriate template
2. **Cross-reference procedures** - automatically link relevant procedures based on keywords
3. **Inject context** - pull in relevant documentation, principles, or procedures
4. **Template selection** - guide agents to use appropriate issue templates

## Implementation Ideas

- [ ] Create procedure: `github-issue-creation.md` with decision tree for issue types
- [ ] Enhance slash commands to incorporate template selection
- [ ] Build mapping between common requests and issue templates
- [ ] Add procedure for agents to scan for relevant context before creating issues

## Example Workflow

User: "create a github issue for improving MCP server logging"

Agent should:
1. Recognize this as a technical enhancement
2. Use appropriate issue template
3. Reference existing MCP procedures
4. Include relevant context from knowledge base

## Acceptance Criteria

- [ ] Procedure documentation created
- [ ] Slash command enhancement (if needed)
- [ ] Issue templates are discoverable by agents
- [ ] Workflow reduces manual template selection
- [ ] Context injection improves issue quality

## Related Principles

- `systems-stewardship` - Building reusable patterns
- `ose` - Operating at the right level of abstraction
- `snowball-method` - Knowledge accumulation through better templates

Start by locating the existing procedures, slash commands, and GitHub issue templates referenced in the issue, then read the proposed github-issue-creation.md procedure. Define how issue-type detection, procedure cross-referencing, template discovery, and context injection should connect; done means the documented workflow and any needed command changes satisfy the listed acceptance criteria.

Written by the indexing model from the issue text.