SWOT Analysis: a Tokeny case study
Synthesize internal and external information to auto-generate SWOT analysis matrices and strategic recommendations. Follow the recorded task, execution screenshots, actual files and verification notes.
By the Tokeny team · Windows · Tokeny 1.7.8 · gpt-6-sol
Prepare the inputs
Create a separate workspace in Tokeny, download and unpack the sample inputs, then select a model that supports tools. The sample uses synthetic data or the public sources named in the article.
- constraints.md
- product-brief.md
Send the task to Tokeny
The original task was executed in Chinese. Copying these instructions reproduces the same task; the results below include an English report.
根据产品简报与内部约束做 SWOT 矩阵，每项说明证据和假设，给出三条可执行策略。 交付文件：swot.html、strategy.md。 验收要点： - 四个象限齐全 - 优势不夸大为市场领先 - 三项行动有负责人角色和衡量方式 这是使用合成演示输入或指定公开资料的真实操作案例。请先读取工作空间输入，再实际生成文件并自检。所有写入、脚本与临时服务限于当前工作空间；临时服务只监听 127.0.0.1，执行后关闭；不触达外部收件人、不发布、不付款、不更改系统设置，不调用子智能体。需要公开资料时可读取给定 URL。只启用完成任务必需的工具。另写 report.md（中文）和 report.en.md（英文），简洁、完整，包含输入、处理步骤、真实结果、检查方式和局限；失败或未验证部分如实记录，不能宣称成功。最终回复用中文列出产物、关键结果与待核实项。 排版检查：Word 主标题仅出现一次，标题为黑色且与后续正文或表格保持同页；Excel 表头和长文字不能被窄列截断，合理设置列宽、换行、行高；HTML 在 390px 视口不能整页横向溢出。报告没有固定字数要求，不要为字数反复改写。
The recorded run used an isolated demonstration workspace. Review the commands and file paths before approving operations in your own workspace.
What actually ran
The task was submitted through the Tokeny input box. An online model read the inputs and executed tools. This run covers the local sample task and its actual files. Results and checks are recorded below.
Results and verification
Inputs
product-brief.md: Songguo Task Board for 3–10-person teams; task list, assignee, due date, and CSV export; free tier up to 3 people and Team tier at RMB 29 per person/month; no mobile app, AI scheduling, or third-party authentication; no invented testimonials, sales, or third-party endorsements.constraints.md: team of 3, monthly budget of RMB 15,000, feedback from 20 demo users; no retention, market-share, or competitor statistics.ENVIRONMENT.md: execution environment and available dependencies only; it does not provide product evidence.
Processing Steps
- Read the workspace files and separated product facts, resource constraints, and prohibited claims.
- Mapped existing capabilities and constraints to strengths and weaknesses; treated user learning and low-cost experiments as opportunities; marked unsupported competitive and demand claims as assumptions within threats.
- Added evidence and assumptions to the SWOT items so product functionality was not overstated as market leadership.
- Defined three executable actions with owner roles, timing, measures, and decision gates.
- Wrote the HTML matrix, strategy Markdown, and bilingual reports.
Actual Results
Created swot.html, strategy.md, report.md, and report.en.md. The matrix has all four quadrants. Strengths describe only capabilities, price, and export support confirmed by the brief; no market-leadership claim was made. The three actions have product, growth/commercial, and technical owner roles plus quantitative measures.
Checks
- Text check: verified the four quadrant headings, three actions, owner roles, measures, and the restrictions against claiming market leadership, sales, retention, market share, or competitor statistics.
- HTML check: verified the responsive CSS, viewport meta tag, one-column layout at 390px, and
box-sizing:border-box. No temporary service was started; the HTML can be opened directly. - Result: static content and layout constraints were checked. No browser automation screenshot or live-user trial was run, so those are not claimed as validated.
Limitations
The analysis uses only the two input files and the existence of feedback from 20 demo users; the feedback text was not provided. There is no retention, conversion, market-share, competitor, or customer-testimonial data. Strategy thresholds are execution hypotheses, not historical benchmarks. The 390px conclusion comes from code-level responsive inspection and was not confirmed with a browser screenshot.
Download and inspect the outputs
The archive contains the files created during this run. Use these checks when adapting the example to your own data.
- Reconcile the reported results against the downloadable sample inputs.
- Open the generated files and check the contents relevant to your task.
- Review the limitations and any unverified steps in the report.