Brite-Nites

@brite-nites source repo

54 skills
0 followers
1 week ago last updated

▌
Situation Mining · brite-nites bundle
Gather public data on a prospect, infer their worldview, and generate 3-4 diagnostic outbound angles that demonstrate understanding instead of pitching. The "diagnostic over promotional" anchor of Brite outbound. Triggers on situation mine, research for outreach, find angles for, diagnostic messaging for, worldview inference, research this prospect, what's going on at this company, hidden signals for, adjacent offering for, entity-specific angles. Hands off to creative-angles Deep Mode (same situation in context), email-copywriting (situation + offer posture), and launch-campaign (via copy artifact). Adapted from Revgrowth1/ai-gtm-workflows workflow 05 (MIT).

1 install
▌
Precedent Search · brite-nites bundle
Searches project-level precedent INDEX files for relevant past decisions. Activates during brainstorming or planning when historical decisions may inform the current approach — searches by keyword against Decision and Tags columns, filters by category, lazy-loads full trace files on match. (Org-level handbook search is currently unavailable.)

1 install
▌
Testing Strategy · brite-nites bundle
Use when writing, reviewing, or refactoring test code. Triggers on Vitest tests, React Testing Library usage, MSW handlers, Playwright E2E tests, pytest fixtures, test structure decisions, or coverage configuration. Contains 46 testing rules across 12 categories.

1 install
▌
Linear Housekeeping · brite-nites
Phase 3 of /cadence:weekly. Derives Linear mutations from Phase 2 scope decisions, re-runs the issue-quality-gate on every cycle-path mutation, previews the batch grouped by decision path + mutation type, and executes atomically with per-group user approval, idempotent pre-flight checks, and an ISO-8601 timestamped audit log. Triggers on "sprint cleanup", "linear housekeeping", "move to cycle", "back to backlog", "batch mutations", "apply scope decisions", or "/cadence:weekly phase 3".

1 install
▌
Campaign Analysis · brite-nites bundle
Diagnose cold email campaign performance via 5 Core Variables (Offer / Message / Segment / Infrastructure / Timing), 4-phase analysis flow, and 6-section report with verdict-mapped recommendations. Mandatory handoff to campaign-debrief. Triggers on analyze campaign, campaign performance, what's working, review campaign, reply rate analysis, performance analysis. Adapted from Revgrowth1/ai-gtm-workflows workflow 11 (MIT).

0 installs
▌
Email Copywriting · brite-nites bundle
Generate Email-Bison-formatted subject + body for step 1 + step 2 from a situation-mining artifact + offer posture + entity. Emits a JSON artifact that the /marketing:launch-campaign command ingests. Triggers on write email copy, draft sequence, email copywriting, generate outbound copy, email drafting for, campaign copy for, EB-format email, per-vertical email preset. Adapted from Revgrowth1/ai-gtm-workflows workflow 10 (MIT).

1 install
▌
Message Market Fit · brite-nites bundle
Run Brite outbound as a truth system using the MSPA matrix (Market × Segment × Persona × Angle) with three modes — MAP for new market entry, ITERATE for post-results iteration, DIAGNOSE for stuck pipeline — under the barbell 80/20 allocation and Kellen's 10 Laws. Serves BDRs, RevOps, and marketing operators who need systematic experiment design, not one-shot campaigns. Triggers on message-market-fit, mmf, test messaging, test angles, which message works, experiment design, what resonates, potency test, MSPA matrix, barbell outbound, stuck pipeline, diagnose outbound, iterate campaign, Kellen's laws. Receives from creative-angles (A dimension of the matrix), campaign-analysis (ITERATE input as `docs/campaigns/{entity}/analysis-*.md`), gtm-strategy (MAP persona profiles), and situation-mining (optional per-account worldview); hands off to outbound-playbook (executes experiments, BC-2722 pending) and campaign-debrief (captures transferable learnings). Adapted from Revgrowth1/ai-gtm-workflows workflow 07 (MIT).

1 install
▌
Salesforce Preload · brite-nites
Create Salesforce Contacts under real business Accounts for a cleaned cold-outbound lead set BEFORE the Email Bison upload, so OutboundSync matches an existing Contact by email instead of deriving a free-email (gmail.com) Account that the AccountTriggerHandler guard rejects. Personal instance only; the instance is an explicit operator-confirmed input. Reads via the read-only Salesforce MCP, writes via the sf CLI. Triggers "salesforce preload", "pre-load leads into salesforce", "preload contacts", "sf preload", "load leads before sending". Distinct from `list-building` (assembles the list) and `tam-mapping` (builds the TAM) — this skill assumes a cleaned list already exists and only mirrors it into Salesforce.

1 install
▌
Compound Learnings · brite-nites bundle
Captures durable knowledge after completing work so future sessions benefit. Activates during the ship phase — updates CLAUDE.md with architectural decisions and gotchas, writes session summary to auto-memory, updates docs if architecture or API changed. Only records genuinely durable facts, not session-specific noise.

1 install
▌
Example Skill · brite-nites
Example skill — replace with your own trigger conditions

1 install
▌
Best Practices Audit · brite-nites bundle
Audits and auto-fixes a project's CLAUDE.md against Anthropic best practices. Activates during ship phase — checks conciseness, enforces @import structure for detailed docs, auto-excludes bloat, identifies hook candidates, and auto-fixes structural issues. Flags content questions for developer review.

1 install
▌
Handbook Drift Check · brite-nites bundle
Detects handbook content that has drifted from project reality after shipping. Activates during the ship phase — compares the shipped diff against handbook files via GitHub API, identifies stale or missing handbook content, and optionally opens a PR to the handbook repo with proposed updates.

1 install
▌
React Best Practices · brite-nites bundle
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

1 install
▌
Systematic Debugging · brite-nites bundle
Four-phase root cause analysis for bug investigation. Activates when debugging unexpected behavior, failing tests, or production issues — follows reproduce, isolate, analyze, fix with defense-in-depth. Uses condition-based waiting instead of arbitrary delays. Available anytime, not tied to the inner loop sequence.

1 install
▌
Gtm Strategy · brite-nites bundle
5-phase net-new GTM motion scoping — research → segments (weighted scoring) → personas → messaging pillars → offer recommendations. Triggers "gtm strategy", "go-to-market plan", "new motion scoping", "segments and personas", "messaging pillars", "new market entry strategy". Distinct from launch-strategy (product launches) and content-strategy (content marketing).

1 install
▌
Code Quality · brite-nites
ESLint, Prettier, Ruff, mypy, and TypeScript strict mode configuration patterns. Use when setting up linting, formatting, or code quality tooling for a new project, reviewing existing configs, generating config files, or adding lint steps to CI. Triggers on tasks involving ESLint, Prettier, Ruff, mypy, Black, code style, linting, formatting, or code quality enforcement.

1 install
▌
List Building · brite-nites bundle
ICP-targeted outbound list assembly. Consumes a TAM source (tam-mapping output, dbt audience CSV, or manual CSV), runs cross-workspace EB exclusion + SF Lead suppression where needed, enriches via the resolved provider, SMTP-verifies, and emits enriched_leads.csv for launch-campaign or campaign-orchestration. Triggers "build list", "list building", "outbound list", "enrich list", "suppress dedup", "ICP list", "decision-maker list", "contact discovery".

1 install
▌
Agent Browser · brite-nites bundle
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.

1 install
▌
Brainstorming · brite-nites bundle
Socratic discovery and design exploration before planning. Activates when objective complexity criteria are met (2+ modules, 4+ tasks, 2+ approaches, or new patterns/integrations) — asks clarifying questions, explores alternatives and tradeoffs, produces a design document for approval. Pulls context from Linear issue description, linked docs, and existing CLAUDE.md learnings.

1 install
▌
Create Issues · brite-nites
Creates Linear issues from a refined project plan. Validates issues were created correctly with sufficient context for agent execution. Use after /refine-plan.

1 install
▌
Git Worktrees · brite-nites bundle
Creates an isolated git worktree for task execution. Activates when starting work on a planned issue — sets up a new branch with Linear issue ID, runs project setup, and verifies a clean test baseline before coding begins.

1 install
▌
Greptile Gate · brite-nites
After a PR is opened (or on demand), read Greptile's 0–5 confidence score and converge the PR toward 5/5 — grill on intent, fix review findings, re-trigger Greptile, loop up to 3 rounds, then run a final independent review. Use during /workflows:ship right after the PR is created, or when the user asks to check the Greptile score, run the Greptile gate, or read/address the Greptile review on a PR. Skips gracefully when Greptile isn't on the repo.

1 install
▌
Writing Plans · brite-nites bundle
Breaks work into bite-sized tasks before coding. Activates when a multi-step task needs planning — creates tasks small enough for a junior developer to follow (2-5 minutes each), with exact file paths, complete implementation details, and verification steps. References Linear issue context and project-specific test commands from CLAUDE.md.

1 install
▌
Creative Angles · brite-nites bundle
Generate non-obvious outbound angles for the 10% experiment allocation of Brite's barbell GTM strategy, scored on an Asymmetry rubric and angle-verdict-mapped (ALPHA / PROMISING / INTERESTING / COMMODITY per ADR-018) with shelf-life warnings on the alpha-bearing tiers. Serves BDRs, RevOps, and marketing operators running experimental campaigns. Triggers on creative gtm, creative angles, hidden signals for, GTM alpha, creative outbound for, non-obvious angles, experimental campaigns. Hands off to email-copywriting (ALPHA angles), message-market-fit / MSPA (populates the A dimension of an MSPA matrix), and content workflows (INTERESTING redirect); receives from situation-mining (Deep Mode prereq). Adapted from Revgrowth1/ai-gtm-workflows workflow 06 (MIT).

1 install
▌
Launch Strategy · brite-nites bundle
Plans product launches, feature announcements, and release strategies. Triggers on launch, Product Hunt, feature release, announcement, go-to-market, beta launch, early access, waitlist, product update, launch checklist, GTM plan, or preparing to ship. For ongoing marketing after launch, see marketing-ideas.

1 install
▌
Executing Plans · brite-nites bundle
Executes a structured plan using subagent-per-task with TDD enforcement. Activates when given an approved plan to implement — launches fresh subagents for each task, enforces red-green-refactor, runs two-stage review per task, and checkpoints between tasks. Parallelizes independent tasks.

1 install
▌
Post Plan Setup · brite-nites
Runs the full post-plan workflow. Refine plan, create Linear issues, setup CLAUDE.md. Use after /plan-project produces a v1 plan. Pauses between phases for optional review.

1 install
▌
Setup Claude Md · brite-nites bundle
Generates a best-practices CLAUDE.md file for the project. Analyzes the codebase and applies Claude Code best practices for optimal agent performance. Use at project setup or after /create-issues.

2 installs
▌
Account Research · brite-nites bundle
Thin orchestrator that dispatches a validated company fact sheet by mode. Serves BDRs, RevOps, and marketing operators doing pre-outreach research who need structured company and people facts without inference, angle generation, or copy. Twelve modes cover 9 single-process invocations (profiles, competitors, growth, hiring, reviews, news, negativity, founders, c-suite) plus 3 composites (full, deep, people), each dispatching to one or more `find-*.md` process files under `plugins/marketing/references/research-processes/`. Triggers on research, research [company], deep research, find info on, company research, people research. Account-research outputs FACTS grouped by dimension (who, what, where, when); situation-mining outputs INFERRED WORLDVIEWS plus angle hypotheses; creative-angles Deep Mode extracts signal clusters into scored angles. Hands off to situation-mining (worldview inference) and creative-angles Deep Mode (signal-cluster extraction); receives from user invocation or situation-mining's fact-gathe

1 install
▌
Campaign Debrief · brite-nites bundle
Structured 5-question post-campaign learning capture (Q1 hypothesis, Q2 result, Q3 what-worked, Q4 surprise, Q5 transferable) that assigns one of four objective campaign verdicts (SCALE / ITERATE / PAUSE / KILL per ADR-018) against concrete numeric thresholds and appends an entry to `docs/campaigns/{short_entity}/learnings.md`. Serves BDRs, RevOps, and marketing operators closing the loop between campaign execution and campaign intelligence. Triggers on debrief, campaign debrief, retro, log campaign, capture learnings. Receives primary input from `campaign-analysis` via `analysis-*.md`; retroactive path pulls metrics standalone from Email Bison when no analysis artifact exists. Hands off transferable learnings to `message-market-fit` (ITERATE Notes column), `product-marketing-context` (cross-entity propagation proposals), and `/workflows:handbook-drift-check` (handbook-contradiction signals). Append-only, forever. Under 5 minutes per debrief. Adapted from Revgrowth1/ai-gtm-workflows workflow 12 (MIT).

1 install
▌
Content Strategy · brite-nites
Develops content marketing strategies and editorial calendars aligned with Brite brand positioning and ICP segments. Reads docs/marketing-context.md for brand context before acting.

1 install
▌
Sf Flow · brite-nites bundle
Creates and validates Salesforce Flows (Brite edition) with 110-point scoring. TRIGGER when user builds or edits record-triggered, screen, autolaunched, or scheduled flows, touches .flow-meta.xml files, works in brite-salesforce, asks about the Apex-first flow policy (Flows only for screen flows + simple notifications), the Screen-Flow-deploy-as-Draft trap (regardless of source `<status>Active</status>`), `sf data update record` failing to activate flows, post-deploy Tooling API verification (`SELECT Status FROM Flow WHERE Definition.DeveloperName = '...'`), scratch-org flow activation gaps, or `/revops:post-deploy-runbook` Phase 2 cross-reference. DO NOT TRIGGER when Apex automation (use sf-apex), process builder migration questions only, or non-Flow declarative config (use sf-metadata).

1 install
▌
Sf Testing · brite-nites bundle
Apex test execution and coverage discipline (Brite edition) with 120-point scoring. TRIGGER when user runs Apex tests, checks coverage, fixes failing tests, touches *Test.cls / *_Test.cls files, works in brite-salesforce, asks about 100% class coverage targets, @TestSetup static-state trap, Queueables inside Test.stopTest() re-entering handlers, @TestVisible + Test.isRunningTest() escape-hatch gating, Bypass_Validation_Rules honoring in tests, LWC Jest pre-commit, or scratch-org-per-PR validation. DO NOT TRIGGER when writing Apex production code (use sf-apex), Agentforce agent testing (use sf-ai-agentforce-testing), or Jest/LWC tests (use sf-lwc).

1 install
▌
Email Bison · brite-nites bundle
Default entry point for Email Bison work. Triggers on Email Bison, cold email, outbound campaign, lead import, sender inbox, warmup, blocklist, unsubscribe, workspace, tag, webhook, template, variable, schedule. Routes to campaign-orchestration (sequence design), reply-processing (inbox classification), or deliverability-audit (SPF/DKIM/DMARC) when the user's intent matches their scope; otherwise handles the long tail inline.

1 install
▌
Icp Scoring · brite-nites bundle
Pre-outreach prospect prioritization — score raw lists 0-100 (with reasoning) or A/B/C tier (Haiku letter-only) against entity-specific ICP criteria. Triggers "icp score", "icp verify", "qualify prospects", "score this list", "rank companies", "tier by icp". Distinct from `lead-routing` (post-reply SF assignment).

1 install
▌
Tam Mapping · brite-nites bundle
Build TAM databases from scratch using a 7-phase methodology (Source Discovery → Keyword Expansion → Config → Collection → Dedup → Exclusion → Enrichment hand-off). Triggers "tam map", "build tam", "total addressable market", "scrape industry", "map the market", "build a lead database", "venue partnerships tam", "labs tam", "residential tam", "installer tam". Entity-routed — Nites residential (Google Maps ZIP), Supply installer (SAM.gov + Houzz + state license dbs), Labs venue partnerships (Spider.cloud + AI Ark + Discolike + IcyPeas + BlitzAPI + Prospeo + MillionVerifier). Phase 4.5 cross-workspace EB exclusion is MANDATORY (HARD-FAIL on either workspace unreachable). Phase 5 enrichment is pluggable per ADR-008. Distinct from `list-building` (BC-2717 — assumes a TAM already exists via dbt audience views).

1 install
▌
Sf Permissions · brite-nites bundle
Salesforce Permission Set / Permission Set Group analysis and access auditing for Brite's brite-salesforce repo. TRIGGER when user asks "who has access to X?", analyzes permsets or permset groups, adds CustomField FLS (7-permset sync reminder), touches Base_CRM_Access or {Team}_Group / {Team}_Management_Group naming, debugs Lifecycle_Stage__c automation-only restrictions, session-based permset activation (HubSpot_Migration, SessionPermissionSetActivation), CreateAuditFields INSERT-only gotcha, or restricted record-type visibility scoping (Acquisition, Partner_Fulfillment). DO NOT TRIGGER when creating new metadata (use sf-metadata), deploying permission sets (use sf-deploy), or Apex-managed sharing logic (use sf-apex).

1 install
▌
Find Skills · brite-nites
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

1 install
▌
Refine Plan · brite-nites
Refines a v1 project plan into agent-ready tasks with clear context, implementation steps, and validation criteria. Use after /plan-project has produced a v1 plan.

1 install
▌
Sprint Scoping · brite-nites
Phase 2 of /cadence:weekly. Sequential per-project scope interview (5 carry-over Qs + 5 scope Qs, one at a time) with brainstorming and the issue-quality-gate. Triggers on "sprint planning", "weekly scope", "what ships this week", "scope the next cycle", or "/cadence:weekly phase 2".

1 install
▌
Sf Data · brite-nites bundle
Salesforce data operations (Brite edition) with 130-point scoring. TRIGGER when user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, works in brite-salesforce, asks about HubSpot migration ETL, email-as-Task migration semantics, setSaveAsActivity Email Logs monitoring, Bulk API session-permset gotchas, CreateAuditFields INSERT-only behavior,

1 install
▌
Social Media Strategy · brite-nites
Creates platform-specific social media strategies aligned with Brite brand voice and audience segments. Reads docs/marketing-context.md for brand context before acting.

1 install
▌
Python Best Practices · brite-nites bundle
Use when writing, reviewing, or refactoring FastAPI/Python backend code. Triggers on FastAPI endpoints, Pydantic models, SQLAlchemy queries, async Python code, or Python API architecture. Contains 38 architectural rules across 8 categories.

1 install
▌
Flow Preflight · brite-nites
Foundation sub-skill for the flow-architecture plugin (implements CDR-023). Runs at the start of every FDA orchestrator (`/flow:start-project`, `/flow:retrofit-project`, `/flow:add-domain`, `/flow:add-sub-flow`, `/flow:audit`) to verify the environment, discover existing FDA artifacts on the filesystem, classify the run mode, confirm Linear scope (writing `.flow/config.json` on first run via the embedded Q36 7-step bootstrap), and emit the Q12.5 structured preamble that downstream sub-skills consume. Read-only EXCEPT the atomic-rename `.flow/config.json` write on first successful confirmation or stale-config replacement.

1 install
▌
Campaign Orchestration · brite-nites bundle
Designs outbound email sequences and orchestrates end-to-end campaign launches in Email Bison. Owns the 8-call canonical launch sequence (create campaign → attach leads → attach senders → schedule → sequence steps → resume), pause/resume/archive, warmup timing, inbox rotation strategy, and send cadence. Triggers on sequence design, inbox rotation, warmup schedule, send cadence, campaign launch, campaign orchestration, attach senders, sequence steps, resume_campaign, archive_campaign, import leads to campaign, allow_parallel_sending, opener, value add, social proof, breakup, A/B variants, step timing, staggered sending. Hands off to email-bison for long-tail workspace ops, deliverability-audit for SPF/DKIM/DMARC and bounce diagnosis, reply-processing for inbound triage, list-building for upstream enrichment, and campaign-analysis for funnel analytics.

1 install
▌
Prospect Temporal Gate · brite-nites
Enforces the Brite Labs 2-cycle/year + 180-day non-repeat hard rule by querying EB workspaces 55+13 plus SF Activity history and emitting a suppression-aware filtered prospect list. Runs as a mandatory pre-enrichment gate inside list-building Workflow 2. Triggers "temporal gate", "180-day check", "non-repeat enforcement", "cycle dedup", "outreach recency suppression".

1 install
▌
Issue Quality Gate · brite-nites
Apply 7 quality checks to a single Linear issue object. Returns pass/fail per check. Phase 1 audit and Phase 2 scope both consume this skill.

1 install
▌
Product Marketing Context · brite-nites
Creates docs/marketing-context.md with foundational marketing context for this project. Triggered by the needs-marketing trait. Read by all other marketing skills before they act.

1 install
▌
Flow Inventory Add · brite-nites
Lightweight inventory append sub-skill for the flow-architecture plugin (implements CDR-023). Two modes — sub-flow-add (append one new flow row under an existing domain) and domain-add (append a fresh domain section via Q19-mini interview). Append-only semantics; never rewrites existing rows; never renames IDs. Triggered by `/flow:add-sub-flow` and `/flow:add-domain`. Sub-flow-add ~30s, domain-add ~5-10 min (interview-paced). Hard-rejects duplicates; sets a state flag for downstream regen-index dispatch.

1 install
▌
Flow Journey Author · brite-nites
Per-domain journey doc authoring sub-skill for the flow-architecture plugin (implements CDR-023). Writes ONE markdown file at `docs/product/journeys/<domain>.md` per domain, conforming to the Q26 locked template (variable phase count per Q26 mod 5; ~290-450+ lines based on TEAM precedent). Hybrid authoring — deterministic frontmatter stamping via the extracted `scripts/build_journey_frontmatter.py` builder (scaffold-log frontmatter + story-doc aggregation per ADR-033, fixture-locked); single body-only `Agent(journey-doc-author)` call for 7-9 narrative sections (single-agent preserves cross-phase narrative continuity). Runs AFTER `flow-doc-author` so story docs are available as authoring context AND as the personas/flow_ids aggregation source. 1 agent per domain; parallel across domains for multi-domain scaffolds with a concurrency cap of ~10 to avoid Claude Code background-agent queueing. 0 synchronous gates in default mode. Per-domain footprint ~90s; wall time scales as `ceil(N/10) * ~90s` — N≤10 domains fin

1 install
▌
Flow Linear Scaffold · brite-nites
Heaviest-mutation sub-skill for the flow-architecture plugin (implements CDR-023). Writes per-domain Linear scaffolding — 1 milestone + N sub-flow parent issues + 5N discipline children + N Children-summary comments + 1 milestone description refresh = 2+7N writes per domain. Per-sub-flow execution unit, per-domain preview/approval. 3-layer idempotency (`.flow/scaffold-log/<domain>.md` append-only + per-sub-flow `list_issues` lookup + MCP error row flag). 100% per-issue fidelity-review coverage via background `Agent(general-purpose)` dispatch with sub-flow-boundary collection (every 6 issues). 1 mandatory pre-scaffold preview gate; conditional gates for failure recovery only. Sub-flow-atomic classified retry on failure (transient -> 1 retry + 2s backoff; permanent -> AskUserQuestion; cascading -> permanent + abort). Preview budget `(2+7N) × 500ms` -> N=10 ~36s, N=30 ~106s.

1 install
▌
Verification Before Completion · brite-nites bundle
Ensures tasks are genuinely resolved before marking them done. Activates at task checkpoints during plan execution — validates that fixes actually work, tests genuinely pass, and acceptance criteria are met. Prevents premature completion declarations.

1 install
▌
Flow Inventory Interview · brite-nites
Greenfield Socratic inventory generator for the flow-architecture plugin (implements CDR-023). Output `docs/product/master-flow-inventory.md` populated with proposed domains + flows. Triggered by `/flow:start-project` (or standalone `/flow:inventory`) when `flow-preflight` mode classifier returns `greenfield`. Five phases — Phase 0 (PROJECT-INTENT priority filter) -> Phase 1 (app-classifier interview, shared with Q11 retrofit) -> Phase 2 (pattern-driven candidate generation, shared) -> skip Phase 3 (no code) -> Phase 4 (greenfield synthesis with 3-tag scope-priority) -> Phase 5 (user confirmation, shared). Per-run footprint ~10-30 min end-to-end (mostly user time).

1 install
▌
Flow Inventory Codebase Scan · brite-nites
Retrofit-mode inventory generator for the flow-architecture plugin (implements CDR-023). Mines code signals (routes, server actions, dialogs, menu items, API endpoints) from an existing Next.js App Router codebase and synthesizes the proposed inventory. Six phases — Phase 0 (PROJECT-INTENT priority filter) -> Phase 1 (app-classifier interview, shared with Q19 greenfield) -> Phase 2 (pattern-driven candidates, shared) -> Phase 3 (deterministic code scan, retrofit-only) -> Phase 4 (synthesis with 4-tag implementation-status taxonomy + value-priority) -> Phase 5 (user confirmation, shared). Framework locked to Next.js App Router for v1. Triggered by `/flow:retrofit-project` when `flow-preflight` mode classifier returns `retrofit`.

1 install

54 published skills