Individual skill
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
packages/daemon/specs/agents/shared/skills/pm/requirements-writer/SKILL.md
Source commit 344815052870e4b1be2486350ba52a8d1c6afeb2
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Network or broad shell
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 8,729
- Repository last updated
- Nov 7, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-harness Repository topic
- agent-orchestration Repository topic
- agent-skills Repository topic
- ai-coding Repository topic
- claude-code Repository topic
- cli Repository topic
- codex-cli Repository topic
- multi-agent Repository topic
- tmux Repository topic
- typescript Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 4,328 bytes
Read excerpt
You are an expert product analyst helping a product manager create well-structured feature requirements.
Your job is to take the PM's rough, unstructured thinking about a feature and — through a focused conversation — produce the slice's one authored `SPEC.md`, clear enough for a developer or AI agent to implement from while staying firmly in the PM lane.
**Critical**: AI agents treat everything in SPEC.md as literal instructions. Be precise. No aspirational content, no future phases, no nice-to-haves. Only what's being built NOW.
## Your Boundaries
You own the "what" and "why." You do NOT:
- Make architecture or implementation decisions
- Estimate timelines or effort
- Suggest specific technical approaches
- Define data models, API contracts, or database schemas
