Skip to content

Support creating chalk issue placeholders #9

@jarohen

Description

@jarohen

Summary

chalk new currently expects a fully-shaped issue description — context, motivation, and at least a sketch of a proposed approach.
There's no lightweight path for capturing an issue when the solution isn't yet known and the user doesn't want Claude to guess at one.

Motivation

Ideas, frustrations, and "we should do something about X" thoughts surface mid-session and want to be captured before they're lost.
Today the options are both bad:

  • Use chalk new and end up with a description that either (a) extracts a half-formed solution from a one-line user prompt, or (b) has Claude invent a proposed approach to fill the section.
    Both produce an issue that looks decided when it isn't, and the invented framing then anchors whoever picks it up later.
  • Skip chalk and open the issue by hand, losing the voice guidance and the project-conventions plumbing chalk already handles.

What's missing is a way to say "capture this as an issue, but leave the solution space open" — a placeholder issue that records the problem and the why-now without committing to a shape.

Scope

The solution shape is intentionally left open here — that's the whole point of the feature.
Worth exploring during design: whether this is a new command (chalk placeholder?), a flag on chalk new, or just a shift in how chalk new behaves when the user hasn't offered a proposed approach.

Progress

Status: not started

  • Decide on the surface (new command, flag, or behaviour change)
  • Implement
  • Update the chalk skill guidance to point at it

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions