file

To draft grounded beads issues, this skill researches specifications and surveys existing code to ensure issues contain real file references, accurate scope, and concrete acceptance criteria before writing. It then outputs structured fields including title, description, design, and acceptance.

Creating software issues with explicit file paths requires surveying project state first. This skill reads your specs and codebase to link concrete file references and draft structured acceptance criteria directly into the issue, ensuring tasks are grounded in reality.

Yes, you can use this skill for task ideation. It investigates specs and existing code during the research phase, asking clarifying questions to define scope and references before drafting the final issue.

Yes, this approach works without adding dependencies. It operates by reading your existing specifications and code to produce structured issue documentation, requiring no additional setup or external libraries.

You structure a beads issue by surveying state and reading specs to populate defined fields. The skill drafts a structured issue containing a title, description, design, and acceptance criteria based on concrete references.

Researching code before writing software issues ensures your tasks are grounded in reality. This skill surveys existing state and specs to link concrete file paths, preventing ungrounded issues and improving task quality.