Add /ultraresearch-local for structured research combining local codebase analysis with external knowledge via parallel agent swarms. Produces research briefs with triangulation, confidence ratings, and source quality assessment. New command: /ultraresearch-local with modes --quick, --local, --external, --fg. New agents: research-orchestrator (opus), docs-researcher, community-researcher, security-researcher, contrarian-researcher, gemini-bridge (all sonnet). New template: research-brief-template.md. Integration: --research flag in /ultraplan-local accepts pre-built research briefs (up to 3), enriches the interview and exploration phases. Planning orchestrator cross-references brief findings during synthesis. Design principle: Context Engineering — right information to right agent at right time. Research briefs are structured artifacts in the pipeline: ultraresearch → brief → ultraplan --research → plan → ultraexecute. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.3 KiB
1.3 KiB
LINKEDIN CONTENT QUALITY GATE: If the file being written/edited is LinkedIn content (a post draft, article, or content file — NOT config files, state files, scripts, or documentation), verify these requirements before proceeding:
Hook Check:
- The first line (hook) MUST be 110-140 characters. Count precisely.
- If over 140: the hook gets cut off on mobile. Shorten it.
- If under 110: wasting prime real estate. Expand it.
Link Check:
- NO external links (http/https URLs) in the post body. LinkedIn suppresses reach by 40-50% for posts with links.
- If a link is needed, instruct the user to put it in the FIRST COMMENT after posting.
Tone Check:
- Scan for corporate buzzwords: 'leverage', 'synergy', 'paradigm shift', 'thought leader', 'disruptive', 'value proposition', 'ecosystem', 'holistic approach', 'actionable insights', 'best practices'.
- If 2+ are found, flag: 'This reads corporate. LinkedIn rewards authentic, conversational tone. Replace buzzwords with plain language.'
Length Check:
- Standard posts: 1,200-1,800 characters optimal.
- Quick posts: 150-500 characters.
- If outside range, flag with specific character count.
Skip this check if the file is a config file, state file (.local.md), script, hook, JSON, or documentation file. Only apply to LinkedIn content.