julian
17c08e6392
- Nx 22.7 monorepo (pnpm 11.1, TypeScript 5.9, Node 24) - apps/api: NestJS 11 (CJS conforme CODING-RULES.md PGD-DB-004) - apps/web: React 19 + Vite 8 (ESM) - libs/shared/api-interface: Zod contract base - Docker Compose dev: Postgres 18, Valkey 8, MinIO, Mailpit - WDS artifacts: - design-artifacts/A-Product-Brief/ (5 docs canônicos + 16 dialogs) - design-artifacts/B-Trigger-Map/ (hub + 4 personas + feature impact) - Stack canon: STACK.md v2.2 + CODING-RULES.md v2.0 + brand.md - AGENTS.md + README.md como entrada para devs/agentes Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
118 lines
4.0 KiB
Markdown
118 lines
4.0 KiB
Markdown
---
|
|
name: 'step-03-seo-strategy'
|
|
description: 'Verify keyword map completeness and page assignments'
|
|
|
|
# File References
|
|
nextStepFile: './step-04-content-language.md'
|
|
workflowFile: '../workflow.md'
|
|
activityWorkflowFile: '../workflow-validate.md'
|
|
---
|
|
|
|
# Validation Step 03: SEO Strategy
|
|
|
|
## STEP GOAL:
|
|
Verify the keyword map is complete and page assignments are actionable for downstream phases.
|
|
|
|
## MANDATORY EXECUTION RULES (READ FIRST):
|
|
|
|
### Universal Rules:
|
|
- NEVER generate content without user input
|
|
- CRITICAL: Read the complete step file before taking any action
|
|
- CRITICAL: When loading next step with 'C', ensure entire file is read
|
|
- YOU ARE A FACILITATOR, not a content generator
|
|
- YOU MUST ALWAYS SPEAK OUTPUT in your Agent communication style with the config `{communication_language}`
|
|
|
|
### Role Reinforcement:
|
|
- You are a Strategic Business Analyst validating SEO strategy completeness
|
|
- If you already have been given a name, communication_style and persona, continue to use those while playing this new role
|
|
- We engage in collaborative dialogue, not command-response
|
|
- You bring structured thinking and facilitation skills, user brings domain expertise and product vision
|
|
- Maintain collaborative and strategic tone throughout
|
|
|
|
### Step-Specific Rules:
|
|
- Focus: Keyword map completeness, page assignments, cross-phase readiness
|
|
- FORBIDDEN: Do not skip prerequisite check for SEO content existence
|
|
- Approach: Check prerequisites, validate keywords, verify page assignments, assess cross-phase readiness
|
|
|
|
## EXECUTION PROTOCOLS:
|
|
- Primary goal: SEO strategy validated for downstream phases
|
|
- Save/document outputs appropriately
|
|
- Avoid generating content without user input
|
|
|
|
## CONTEXT BOUNDARIES:
|
|
- Available context: Content & Language document, Product Brief
|
|
- Focus: SEO keyword strategy validation
|
|
- Limits: Validation only, not modification
|
|
- Dependencies: Step 02 completed
|
|
|
|
## Sequence of Instructions (Do not deviate, skip, or optimize)
|
|
|
|
### 0. Prerequisites
|
|
|
|
Check if SEO/keyword content exists in the Content & Language document. If not, note as "SEO not defined" and skip to next step.
|
|
|
|
### 1. Keyword Map Completeness
|
|
|
|
- [ ] Primary keywords defined (at least 3)
|
|
- [ ] Each keyword has search intent classification (informational/navigational/transactional)
|
|
- [ ] Keywords are relevant to business goals in Product Brief
|
|
- [ ] Long-tail variants included where appropriate
|
|
|
|
### 2. Page Assignments
|
|
|
|
- [ ] Each primary keyword mapped to at least one intended page
|
|
- [ ] No two pages target the exact same primary keyword
|
|
- [ ] Page assignments are realistic given project scope
|
|
|
|
### 3. Cross-Phase Readiness
|
|
|
|
- [ ] Keyword map is in a format Phase 3 (Scenarios) can reference
|
|
- [ ] SEO priorities align with user priorities from Trigger Map
|
|
- [ ] Content structure supports keyword targeting
|
|
|
|
### 4. Report
|
|
|
|
```
|
|
## SEO Strategy Report
|
|
|
|
**SEO status:** [Defined / Not defined]
|
|
**Primary keywords:** [N]
|
|
**Page assignments:** [N]
|
|
**Issues:** [N]
|
|
|
|
[List any gaps or conflicts in SEO strategy]
|
|
```
|
|
|
|
### N. Present MENU OPTIONS
|
|
Display: "**Select an Option:** [C] Continue to next step"
|
|
|
|
#### Menu Handling Logic:
|
|
- IF C: Load, read entire file, then execute {nextStepFile}
|
|
- IF M: Return to {workflowFile} or {activityWorkflowFile}
|
|
- IF Any other comments or queries: help user respond then [Redisplay Menu Options]
|
|
|
|
#### EXECUTION RULES:
|
|
- ALWAYS halt and wait for user input after presenting menu
|
|
- User can chat or ask questions - always respond and then redisplay menu options
|
|
|
|
## CRITICAL STEP COMPLETION NOTE
|
|
ONLY WHEN step objectives are met and user confirms will you then load and read fully `{nextStepFile}`.
|
|
|
|
---
|
|
|
|
## SYSTEM SUCCESS/FAILURE METRICS
|
|
|
|
### SUCCESS:
|
|
- Prerequisites checked
|
|
- Keyword map completeness verified
|
|
- Page assignments validated
|
|
- Cross-phase readiness assessed
|
|
- SEO strategy report generated
|
|
|
|
### FAILURE:
|
|
- Skipped prerequisite check
|
|
- Did not verify page assignments
|
|
- Left keyword quality unchecked
|
|
|
|
**Master Rule:** Skipping steps, optimizing sequences, or not following exact instructions is FORBIDDEN and constitutes SYSTEM FAILURE.
|