alexago83/logics-product-brief-writer
logics-product-brief-writer/SKILL.md
Write product briefs in `logics/product`. Use when Codex identifies a structuring product framing need (user problem, target users, scope, trade-offs, success signals) and should create a concise product decision document linked to request/backlog/task docs.
$ install --global
skillsauthnpx skillsauth add alexago83/cdx-logics-kit logics-product-brief-writerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 10, 2026, 3:08 AM30.9s4 files scanned
SKILL.md
- name:
- logics-product-brief-writer
- description:
- Write product briefs in `logics/product`. Use when Codex identifies a structuring product framing need (user problem, target users, scope, trade-offs, success signals) and should create a concise product decision document linked to request/backlog/task docs.
Product brief
Create a new product brief
python logics/skills/logics-product-brief-writer/scripts/new_product_brief.py --title "Guest checkout framing" --out-dir logics/product
Structure
- Use
# Overviewto state the product direction in 3 to 5 short lines. - Keep the Mermaid in
# Overviewmacro-level only: user problem -> chosen product direction -> expected outcomes. - Keep the document product-only: user value, scope, trade-offs, success signals, open questions.
- Do not drift into implementation design or system internals. Link to
logics/architecture/when a technical decision is also required.
Update discipline
- When you edit an existing product brief, update
Statusand every impacted linked ref (request,backlog,task,architecture). - Keep
# Scope and guardrails,# Key product decisions,# Success signals, and# Open questionsaligned with the latest product direction. - Remove stale placeholders and replace the
# OverviewMermaid when the direction materially changes.
Related Skills
alexago83/logics-mermaid-generator
data-ai
VerifiedTrustedCommunity
Generate Logics workflow Mermaid blocks with a deterministic fallback that stays compatible with the flow manager.
1SKILL.mdUpdated Apr 10, 2026
alexago83/fixture-valid-skill
testing
VerifiedTrustedCommunity
Fixture skill used to validate Logics kit package parsing.
1SKILL.mdUpdated Apr 2, 2026
alexago83/tests/fixtures/skill_package_invalid
testing
VerifiedTrustedCommunity
--- name: fixture-invalid-skill description: invalid: yaml frontmatter sample --- # Fixture Invalid Skill This fixture intentionally violates the SKILL frontmatter contract.
1SKILL.mdUpdated Apr 2, 2026
alexago83/logics-workstream-planner
development
VerifiedTrustedCommunity
Plan workstreams/roadmap from Logics backlog and tasks. Use when Codex should generate a `logics/ROADMAP.md` grouping items into Now/Next/Later/Done based on priority and progress.
1SKILL.mdUpdated Apr 2, 2026