featurelisted
Install: claude install-skill varuntej07/tej-stack
# Feature
Feature request: the user's message.
**Setup.** Read `.context/tej-core.json` (`repos` in scope, `never_touch` folders you must never
read or edit) and `.claude/rules/project-workflow.md` (this repo's suites, evals, contract doc,
in-flight audit and UI rules). If `.context/tej-core.json` is missing, say so in one line and
offer `/tej-core:init` first. Specs live in the `.context/2-specs/` of the repo this session runs
in.
## Phase 1: Understand (read-only)
1. Map every path the feature touches to its doc with the lookup table in `CLAUDE.md`. Read each
`.context/1-docs/ARCH-*.md` in full, plus the contract doc `project-workflow.md` names when a
cross-repo contract is involved.
2. Read the live code on every touched path in every repo in `repos`. Check the in-flight audit
(`.context/2-specs/IN-FLIGHT-AUDIT.md`) for overlapping uncommitted or undeployed work.
3. Test the idea against "what if the user asks something I did not anticipate?": prefer one
generic primitive (capability as data) over a hardcoded vertical codepath.
## Phase 2: Spec
4. If a `*_PLAN.md` for this work already exists at a repo root, THAT file is the deliverable:
revise it in place with a Context section, add the template's sections, and point a short
`SPEC-<slug>.md` stub (frontmatter plus acceptance boxes) at it. Otherwise copy
`.context/2-specs/_TEMPLATE-feature.md` to `.context/2-specs/SPEC-<slug>.md` and fill every
section: taxonomy with MUST NOT rows, ASCII block d