Resolve stash conflicts: keep upstream + local deploy wiring checks
Some checks failed
CI / pr-title (push) Has been cancelled
CI / test (push) Has been cancelled
Release PR / release-pr (push) Has been cancelled
Release PR / publish-cli (push) Has been cancelled

Merge upstream's ce-brainstorm skip-menu guidance and ce-plan
repo-research-analyst integration with local deploy wiring flag
additions.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
John Lamb
2026-03-25 13:35:02 -05:00
parent 8279c8ddc3
commit 6695dd35f7
4 changed files with 5 additions and 5 deletions

View File

@@ -7,11 +7,6 @@ description: This skill should be used when the user wants to create a Jira tick
Write Jira tickets that sound like a human wrote them. Drafts go through tone review before the user sees them, and nothing gets created without explicit approval.
## Reference
For tickets pertaining to Talent Engine (Agentic App), TalentOS, Comparably, or the ATS Platform: Use the `ZAS` Jira project
When creating epics and tickets for Talent Engine always add the label `talent-engine` and prefix the name with "[Agentic App]"
When creating epics and tickets for the ATS Platform always add the label `ats-platform` and prefix the name with "[ATS Platform]"
## Workflow
### Phase 1: Validate Scope