SWOT Scope - AFPS Tracker
Stage 1 scope approval for $competitive-analysis/frameworks/swot. This page proposes the research boundary, source plan, assumptions, and output paths only. It does not contain SWOT findings, competitor rankings, recommendations, a working packet, or a canonical framework artifact.
Scope Evidence
The active competitive-analysis queue already approved AFPS Tracker as the scoped product path and explicitly excluded exec-loop-tracker. SWOT is the next unchecked framework after the confirmed Porter Five Forces artifact.
| Evidence | Path | Stage 1 Use | Boundary Note |
|---|---|---|---|
| Parent competitive-analysis packet | research/afps-tracker/_working/preliminary-competitive-analysis-research.md |
Defines approved AFPS Tracker-only competitive-analysis scope and child framework queue. | Scope evidence only; child framework findings remain gated. |
| Canonical ICP | research/afps-tracker/icp.md |
Defines primary ICP as AFPS power users and AI workflow operators. | Strength and weakness evidence in Stage 2 must still be grounded in actual repo/product artifacts. |
| Confirmed Porter artifact | research/afps-tracker/competitive-analysis-porter-five-forces.md |
Provides approved market boundary and structural source categories. | May inform source coverage; SWOT must not simply restate Porter scores. |
| Progress manifest | research/.progress.yaml |
Shows research/afps-tracker and research/exec-loop-tracker as active paths. |
This SWOT lane targets only research/afps-tracker. |
| Current task queue | tasks/todo.md |
Shows SWOT as the next unchecked approved framework. | Strategic-group-map, feature-pricing-matrix, and synthesis remain later queued steps. |
Proposed SWOT Research Scope
AFPS Tracker: a companion sync layer and passive portfolio map for the alignment-first, prototype-second skills workflow.
AFPS power users and AI workflow operators managing repo-local research state, alignment pages, product paths, and task context.
Strengths and weaknesses from internal product/repo/research evidence; opportunities and threats from market, competitor, customer, and trend evidence.
No execution-tracker scope, no positioning recommendation, no product roadmap, and no canonical synthesis in this framework lane.
Source Plan
After scope approval, SWOT research should use breadth-first current web search plus repo evidence. Competitor or market facts may not be used as findings unless sourced.
| Category | Examples To Search | Likely SWOT Use | Evidence Standard |
|---|---|---|---|
| Repo/product evidence | Idea brief, ICP, parent packet, progress manifest, task history, existing framework artifacts | Strengths, weaknesses, scope boundaries | Path-cited local artifact observations |
| Direct alternatives and workaround bundles | Manual repo navigation, alignment/index.html, research/.progress.yaml, memory/status files | Weaknesses, threats, substitute pressure | Repo evidence and explicit caveats where no external vendor exists |
| Generic workspaces and project tools | Notion, Linear, Trello, Jira | Threats and opportunity contrast | Vendor pages, docs, pricing, recent updates |
| Product discovery and research repositories | Jira Product Discovery, Productboard, Dovetail, Condens | Opportunities, threats, adjacent WTP | Vendor pages, pricing, integrations, case studies |
| AI coding agents and agent-control planes | Claude Code, GitHub Copilot, Kiro, Runshift, Linear agents | Market threats and trend opportunities | Vendor pages, launch notes, docs, user sentiment |
| User sentiment and community language | Developer surveys, forums, product communities, public discussions | Opportunities, threats, confidence caveats | Recent sources preferred; cite limits and uncertainty |
Assumptions And Confidence
| Assumption | Status | Confidence | Stage 2 Test |
|---|---|---|---|
| AFPS Tracker should stay scoped to research-stage AFPS workflow state. | Approved parent scope | High | Use as boundary unless approval YAML changes it. |
| Strengths and weaknesses can be assessed from current repo and approved research artifacts. | Provisional | Medium | Check actual artifacts for present capabilities, not aspirations. |
| Opportunities and threats should be grounded in broader AI workflow, product discovery, and research repository evidence. | Evidence-informed scope assumption | Medium | Validate with current web sources during Stage 2. |
| Direct AFPS-specific market evidence may remain sparse. | Known coverage risk | Medium-high | Flag direct-evidence gaps separately from adjacent-category evidence. |
| Approved Porter evidence can inform SWOT source coverage but should not substitute for SWOT-specific analysis. | Process constraint | High | Use Porter as context, not as the SWOT artifact. |
Proposed Output Paths
| Path | Stage | Action Now | Action After Approval |
|---|---|---|---|
alignment/swot-afps-tracker.html | Stage 1 | Create review page | Update for Stage 2 artifact review after scope approval |
research/afps-tracker/_working/preliminary-swot-research.md | Stage 2 | Do not create yet | Create only after final compiled scope approval YAML |
research/afps-tracker/competitive-analysis-swot.md | Stage 3 | Do not create yet | Create only after artifact approval YAML |
alignment/index.html | Index | Add this review page | Keep status current as the page advances |
tasks/todo.md and tasks/roadmap.md | Task tracking | Record Stage 1 scope approval progress | Record verification and next gated state |
Research Scope Approval Gates
This page should be approved only if the next step is allowed to perform synthesized SWOT research and write the non-canonical Stage 2 working packet. Feedback-only YAML may request revisions without answering every gate.
Pre-approval stop: The next action is review of this HTML page. Stage 2 does not start until final compiled YAML answers all required gates without unresolved needs-clarification, unresolved negative feedback, or other unresolved blocking changes.
Compile Review YAML
Use feedback-only YAML for emphasis requests, concerns, or clarification before final approval. Use final compiled answers when every required gate is answered.
Required questions remaining: 4