User Story Writer
deanpeters/Product-Manager-Skills
Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.
A skill your agent uses when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code
Install Investigating Codebase For User Stories
$ npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install aaddrick/claude-pipeline investigating-codebase-for-user-stories --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/investigating-codebase-for-user-stories .claude/skills/investigating-codebase-for-user-stories && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "investigating-codebase-for-user-stories" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/investigating-codebase-for-user-stories into .claude/skills/investigating-codebase-for-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-codebase-for-user-stories", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/investigating-codebase-for-user-storiesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install aaddrick/claude-pipeline investigating-codebase-for-user-stories --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/investigating-codebase-for-user-stories .agents/skills/investigating-codebase-for-user-stories && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "investigating-codebase-for-user-stories" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/investigating-codebase-for-user-stories into .agents/skills/investigating-codebase-for-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-codebase-for-user-stories", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install aaddrick/claude-pipeline investigating-codebase-for-user-stories --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/investigating-codebase-for-user-stories .cursor/skills/investigating-codebase-for-user-stories && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "investigating-codebase-for-user-stories" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/investigating-codebase-for-user-stories into .cursor/skills/investigating-codebase-for-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-codebase-for-user-stories", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/aaddrick/claude-pipeline.git --path .claude/skills/investigating-codebase-for-user-stories--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install aaddrick/claude-pipeline investigating-codebase-for-user-stories --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/investigating-codebase-for-user-stories .gemini/skills/investigating-codebase-for-user-stories && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "investigating-codebase-for-user-stories" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/investigating-codebase-for-user-stories into .gemini/skills/investigating-codebase-for-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-codebase-for-user-stories", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install aaddrick/claude-pipeline investigating-codebase-for-user-storiesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/investigating-codebase-for-user-stories .github/skills/investigating-codebase-for-user-stories && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "investigating-codebase-for-user-stories" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/investigating-codebase-for-user-stories into .github/skills/investigating-codebase-for-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-codebase-for-user-stories", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install aaddrick/claude-pipeline investigating-codebase-for-user-stories --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/investigating-codebase-for-user-stories .opencode/skills/investigating-codebase-for-user-stories && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "investigating-codebase-for-user-stories" agent skill from https://github.com/aaddrick/claude-pipeline/tree/main/.claude/skills/investigating-codebase-for-user-stories into .opencode/skills/investigating-codebase-for-user-stories/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "investigating-codebase-for-user-stories", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
investigating-codebase-for-user-stories- GitHub stars
- 130
- Token cost
- ~2.2k tokens
- SKILL.md length
- 504 words
- Files
- 1
- Skills in repo
- 12
- Repo updated
- First seen
- Licence
- MIT
At a glance
A skill your agent uses when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code
- Works in 7 steps: Identify User Types → Map Feature Areas → Trace User Journeys → …
- Asked to create user stories from a codebase
- SKILL.md covers Overview, When to Use, Investigation Phases and Phase 1: Identify User Types, plus 9 more sections
- Calls gh
What it does
Investigating Codebase For User Stories is an agent skill from aaddrick/claude-pipeline. Use when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code
Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Product & Project Management, covering User stories. The repository describes itself as: Portable Claude Code multi-agent pipeline - skills, agents, hooks, orchestration scripts, and quality gates. The licence is MIT.
When your agent uses it
- Asked to create user stories from a codebase
- Document existing features as stories
- Reverse-engineer requirements from code
Example prompts
- “/investigating-codebase-for-user-stories”
Workflow steps
7 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 402eac7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Investigating Codebase For User Stories loads about 2.2k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 504 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from aaddrick/claude-pipeline at commit 402eac7, republished under its MIT licence (© aaddrick). 504 words, ~2,179 tokens.
Download SKILL.mdSave it as
.claude/skills/investigating-codebase-for-user-stories/SKILL.md (or your agent's skills folder).- name
- investigating-codebase-for-user-stories
- description
- Use when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code
Investigating Codebase for User Stories
Overview
Systematic codebase investigation to produce well-formed user stories with acceptance criteria and traceability. Prevents shallow exploration that misses features or produces untestable stories.
When to Use
- Asked to "create user stories from this codebase"
- Need to document existing features as stories
- Reverse-engineering requirements from implementation
- Onboarding to understand what a system does
Investigation Phases
digraph investigation {
rankdir=TB;
node [shape=box];
identify [label="1. Identify User Types\n(routes, auth, controllers)"];
map [label="2. Map Feature Areas\n(by controller/domain)"];
trace [label="3. Trace User Journeys\n(entry points → outcomes)"];
write [label="4. Write Stories\nwith Acceptance Criteria"];
validate [label="5. Validate Coverage\n(cross-check routes/views)"];
deps [label="6. Map Dependencies\n(blocks/blocked-by)"];
save [label="7. Save to Files\n(docs/user-stories/)"];
identify -> map -> trace -> write -> validate -> deps -> save;
}Phase 1: Identify User Types
Investigate authentication and authorization to find distinct user types:
| Look In | What to Find |
|---|---|
| Middleware | Auth guards, role checks, permission gates |
| Routes | Route groups with different middleware |
| User model | Roles, groups, subscription tiers |
| Views/layouts | Different dashboards, nav menus |
Output: List of user types (e.g., Guest, Registered User, Admin, Subscriber)
Phase 2: Map Feature Areas
Group functionality by domain, not by file structure:
Feature Area | Controllers/Services | User Types
---------------------|-----------------------------|-----------
Authentication | AuthController, MfaController| All
Product Catalog | ProductController, SearchController| Registered+
Notifications | NotificationController | Subscriber+
Admin Management | AdminController | AdminKey locations to scan:
routes/web.php,routes/api.php- all endpointsapp/Http/Controllers/- feature groupingsresources/views/- UI capabilities- Database migrations - data model capabilities
Phase 3: Trace User Journeys
For each feature area, trace complete user journeys:
- Entry point - How does user reach this feature?
- Actions available - What can they do?
- State changes - What data changes?
- Outcomes - What feedback/result do they see?
Document with code references: NotificationController:45 for traceability.
Phase 4: Write Stories with Acceptance Criteria
Story Format
**As a** [specific user type from Phase 1],
**I want** [action/capability traced in Phase 3],
**so that** [business value/outcome].
**Acceptance Criteria:**
- [ ] Given [precondition], when [action], then [outcome]
- [ ] Given [alternate precondition], when [action], then [different outcome]
- [ ] Edge case: [boundary condition handling]
**Code References:** ControllerName:line, ViewName.blade.php
**Complexity:** S/M/L (based on code paths and integrations)Sizing Heuristics
| Size | Indicators |
|---|---|
| S | Single controller method, no external integrations |
| M | Multiple methods, 1-2 integrations, some branching |
| L | Cross-cutting, multiple services, complex state |
Phase 5: Validate Coverage
Cross-check stories against:
- All routes have corresponding stories
- All views have corresponding stories
- All user types have stories
- No orphan features (code without stories)
Phase 6: Map Dependencies
Identify which stories depend on others:
Story A (Auth) ─────► Story B (Notifications)
"User must be authenticated"
Story C (Admin) ────► Story D (User Management)
"Admin role required"Dependency types:
- Blocks: Story must complete before another can start
- Relates to: Stories share code/features but are independent
- Duplicates: Overlapping functionality (merge or clarify scope)
Add to each story file:
## Dependencies
- **Blocked by:** [guest-signup](../authentication/guest-signup.md)
- **Blocks:** [subscriber-export-data](../account/subscriber-export-data.md)Show full SKILL.md (208 more words)Show less
Phase 7: Save to Files
- Create directory structure:
mkdir -p docs/user-stories/{feature-areas} - Write each story to its own file using naming convention
- Generate
README.mdindex with coverage matrix and links - Include dependency graph in README
Output Structure
Save stories as separate markdown files in docs/user-stories/:
docs/user-stories/
├── README.md # Index with coverage matrix
├── authentication/
│ ├── guest-signup.md
│ ├── guest-login.md
│ └── user-logout.md
├── notifications/
│ ├── user-create-notification.md
│ └── user-manage-notifications.md
└── admin/
└── admin-manage-users.mdFile Naming Convention
{user-type}-{action-verb}-{feature}.md
Examples:
guest-complete-eligibility.mdsubscriber-configure-notifications.mdadmin-reset-user-password.md
Individual Story File Template
# {Story Title}
**As a** {user type},
**I want** {capability},
**so that** {benefit}.
## Acceptance Criteria
- [ ] Given {precondition}, when {action}, then {outcome}
- [ ] Given {alternate}, when {action}, then {different outcome}
- [ ] Edge case: {boundary condition}
## Dependencies
- **Blocked by:** [story-name](../feature/story-name.md)
- **Blocks:** [other-story](../feature/other-story.md)
- **Relates to:** [related-story](../feature/related-story.md)
## Code References
| Component | Location |
|-----------|----------|
| Controller | `AppController:45` |
| View | `feature.blade.php` |
| Model | `Feature.php` |
## Complexity
**Size:** S/M/L
**Rationale:** {why this size}README.md (Index File)
# User Stories: {Project Name}
Generated: {date}
## Coverage Matrix
| Feature Area | Guest | User | Admin | Stories | Routes |
|--------------|-------|------|-------|---------|--------|
| Auth | 3 | 2 | 1 | 6 | 8/8 |
## Dependency Graph
```mermaid
graph LR
A[guest-signup] --> B[user-create-notification]
A --> C[user-view-products]
B --> D[subscriber-export-data]
C --> DStories by Feature Area
Authentication
Notifications
## GitHub Issue Output
Generate stories as GitHub issues for sprint planning:
### Single Issue Creation
```bash
gh issue create \
--title "As a guest, I want to sign up" \
--body "$(cat docs/user-stories/authentication/guest-signup.md)" \
--label "user-story,feature-area:auth,size:M"Batch Issue Creation Script
Generate create-issues.sh alongside stories:
#!/bin/bash
# Auto-generated from user stories
gh issue create --title "Guest Signup" \
--body-file docs/user-stories/authentication/guest-signup.md \
--label "user-story,auth,size:S"
gh issue create --title "User Create Notification" \
--body-file docs/user-stories/notifications/user-create-notification.md \
--label "user-story,notifications,size:M" \
--milestone "Sprint 2"Recommended Labels
Create these labels in your repo:
| Label | Description |
|---|---|
user-story | All user stories |
size:S / size:M / size:L | Complexity |
blocked | Has unresolved dependencies |
feature-area:{name} | Feature grouping |
Common Mistakes
| Mistake | Fix |
|---|---|
| Listing code features, not user capabilities | Start from user types, not controllers |
| Missing acceptance criteria | Every story needs Given/When/Then |
| No traceability | Include file:line references |
| Flat list without grouping | Group by feature area → user type |
| Assumed user types | Verify from auth/middleware code |
| Missing edge cases | Check error handlers, validation rules |
| All stories in one file | Separate file per story in docs/user-stories/ |
| No index/README | Always generate README.md with coverage matrix |
| Missing dependencies | Trace auth/middleware chains for implicit blocks |
| Circular dependencies | Indicates stories need to be split or merged |
| No GitHub labels | Create labels before running batch issue script |
© aaddrick, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/investigating-codebase-for-user-stories of aaddrick/claude-pipeline.
Open the folder on GitHubat commit 402eac7
Compare with similar skills
Investigating Codebase For User Stories next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Investigating Codebase For User Stories this skillaaddrick/claude-pipeline | 130 | — | ~2.2k | Automated safety check: Pass | MIT | |
| User Story Writerdeanpeters/Product-Manager-Skills | 7.2k | 2 repos | ~2.9k | Automated safety check: Pass | Custom licence | |
| Ralph Tui Create Beadssubsy/ralph-tui | 2.5k | 1 repos | ~2.6k | Automated safety check: Pass | MIT | |
| Agile Product Owneralirezarezvani/claude-skills | 28k | 3 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Ralph Tui Create Beads Rustsubsy/ralph-tui | 2.5k | 1 repos | ~2.8k | Automated safety check: Pass | MIT | |
| To Specbestofjs/bestofjs | 3.1k | 21 repos | ~757 | Automated safety check: Pass | MIT |
Similar skills
Ralph Tui Create Beads
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.
Agile Product Owner
alirezarezvani/claude-skills
Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.
Ralph Tui Create Beads Rust
subsy/ralph-tui
Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).
To Spec
bestofjs/bestofjs
Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.
Ralph Tui Create JSON
subsy/ralph-tui
Convert PRDs to prd.json format for ralph-tui execution. An agent skill from subsy/ralph-tui.
More from aaddrick/claude-pipeline
All 12 skills in this repoWriting Agents
aaddrick/claude-pipeline
A skill your agent uses when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool
Adapting Claude Pipeline
aaddrick/claude-pipeline
A skill your agent uses when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack…
Review UI
aaddrick/claude-pipeline
Comprehensive UI/CSS review using parallel agents. An agent skill from aaddrick/claude-pipeline.
Using Git Worktrees
aaddrick/claude-pipeline
A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in .worktrees/
Implement Issue
aaddrick/claude-pipeline
A skill your agent uses when given a GitHub issue number and base branch to implement end-to-end
Write Docblocks
aaddrick/claude-pipeline
A skill your agent uses when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files
Related
Categories
Questions about Investigating Codebase For User Stories
What does Investigating Codebase For User Stories do?
A skill your agent uses when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code. Investigating Codebase For User Stories is an agent skill from aaddrick/claude-pipeline.
When should I use Investigating Codebase For User Stories?
Investigating Codebase For User Stories fits situations like: asked to create user stories from a codebase; document existing features as stories; reverse-engineer requirements from code.
How do I install Investigating Codebase For User Stories in Claude Code?
Run `npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a claude-code`. Or copy the skill folder (.claude/skills/investigating-codebase-for-user-stories in aaddrick/claude-pipeline) into .claude/skills/investigating-codebase-for-user-stories in your project. Claude Code loads it when a task matches its description.
How do I install Investigating Codebase For User Stories in Codex?
Run `npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a codex`. Or copy the skill folder (.claude/skills/investigating-codebase-for-user-stories in aaddrick/claude-pipeline) into .agents/skills/investigating-codebase-for-user-stories in your project. Codex loads it when a task matches its description.
Can I use Investigating Codebase For User Stories in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aaddrick/claude-pipeline --skill investigating-codebase-for-user-stories -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/investigating-codebase-for-user-stories, .gemini/skills/investigating-codebase-for-user-stories, .github/skills/investigating-codebase-for-user-stories and .opencode/skills/investigating-codebase-for-user-stories in your project.
What does Investigating Codebase For User Stories need to run?
Going by SKILL.md and its folder, Investigating Codebase For User Stories needs the command-line tools its instructions call (gh).
Does Investigating Codebase For User Stories access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Investigating Codebase For User Stories safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Investigating Codebase For User Stories use?
Investigating Codebase For User Stories is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Investigating Codebase For User Stories use?
About 2.2k tokens (SKILL.md is roughly 8.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Investigating Codebase For User Stories?
Skills that share tags, products or a category with Investigating Codebase For User Stories: User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars), Agile Product Owner (alirezarezvani/claude-skills, 28k stars) and Ralph Tui Create Beads Rust (subsy/ralph-tui, 2.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Investigating Codebase For User Stories?
aaddrick (a GitHub user) maintains it in aaddrick/claude-pipeline, which has 130 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on February 25, 2026.
Source: aaddrick/claude-pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.