Ground user ideas in repo state and C3 architecture into implementable Stories.
npx skills add https://github.com/thewind121212/natashi --skill topic-creator
Please help me install this Agent Skill. Skill: topic-creator Source: https://github.com/thewind121212/natashi/tree/main/.claude/skills/topic-creator Command: npx skills add https://github.com/thewind121212/natashi --skill topic-creator
Quickly convert vague ideas into small, implementable dev Stories that are grounded in the actual repo and docs, reducing hallucinations and misalignment.
Ground the idea in the repository reality and generate a concise, one-day dev Story in docs/stories.
High-intent search queries and answers about installing and using this skill.
Generating a development story involves grounding your idea in the repository's current state and C3 architecture. It outputs a scoped story file in docs/stories with clear acceptance criteria, designed to be completed in a single work session of one day or less.
To create a one-day dev story, define a small, low-risk scope with clear acceptance criteria. You output a story file in docs/stories that specifies required evidence references and constraints on affected components and inputs.
The best way to write aligned requirements is to ground your ideas in the actual repository state and C3 architecture. This ensures the documented story file accurately reflects the current codebase, reducing misalignment and hallucinations.
Yes, an existing C3 architecture and repository state are required. The story generation process grounds your idea in these architectural realities to accurately define scope, acceptance criteria, and constraints on affected components.
Development stories exceed a single session when they lack grounding in the repository state and C3 architecture. Generating a focused story constrains the scope to a single work session by defining clear acceptance criteria and limiting affected components.
Deland78Convert a story concept file into a canon/story-arc.md artifact.
bybren-llcEnforce evidence collection and phase-specific templates for Linear ticket management.
lagz0neQuery C3 IDs to locate and explain architecture across documentation and code.
royhenengelGenerate spec-driven implementation plans for software development tasks.
