write-idea
/write-idea
Turns a person's request into a lengua idea file, idea.md (and ideas/<module>.md, ideas/ui/<screen>.md for a larger program), with its purpose, its behaviours as Given/When/Then tests with examples, its constraints (the grants) and its structure, in ASD-STE100 Simplified Technical English, then calls the check tool until it reports no problems. Use when a person asks for a new lengua program or a change to one.
- Author
- laughing-hermit ↗
- Repository
- lengua ↗
- Licence
- Apache-2.0
- Last repository change
- 13.11.2026
Assessment and security
- Files in this package
- 3
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 13.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Turns a person's request into a lengua idea file, idea.md (and ideas/<module>.md, ideas/ui/<screen>.md for a larger program), with its purpose, its behaviours as Given/When/Then tests with examples, its constraints (the grants) and its structure, in ASD-STE100 Simplified Technical English, then calls the check tool until it reports no problems. Use when a person asks for a new lengua program or a change to one.
Original author description
Turns a person's request into a lengua idea file, idea.md (and ideas/<module>.md, ideas/ui/<screen>.md for a larger program), with its purpose, its behaviours as Given/When/Then tests with examples, its constraints (the grants) and its structure, in ASD-STE100 Simplified Technical English, then calls the check tool until it reports no problems. Use when a person asks for a new lengua program or a change to one.
How it works
- Steps
- A small idea
SKILL.md preview
---
name: write-idea
description: Turns a person's request into a lengua idea file, idea.md (and ideas/<module>.md, ideas/ui/<screen>.md for a larger program), with its purpose, its behaviours as Given/When/Then tests with examples, its constraints (the grants) and its structure, in ASD-STE100 Simplified Technical English, then calls the check tool until it reports no problems. Use when a person asks for a new lengua program or a change to one.
license: Apache-2.0
---
# write-idea
An idea file is the program's only documentation and the source of its tests. Write it so
that the MCP tool `check` reports no problems. The full grammar is in `Lengua3.md`, section 4,
"The idea file's grammar".
## Steps
1. Read the request. Decide what the program reads, what it writes, and what it may touch.
2. Make the folder. Write `idea.md` with these four sections, in this order:
- `# Purpose`: what the program is for, in a few short sentences.
- `# Behaviours`: one `## name` per behaviour, with a `Given`, a `When` and a `Then` line,
then one `### Example: name` block or more. See
[the test format](references/test-format.md).
- `# Constraints`: one `- Key: value` line each. The top idea always has `- Memory:` and
`- Time:`. Grant only what the program needs: `- Reads: standard input`,
``- Reads: files in `data/` ``, ``- Writes: files in `out/` ``,
``- Connects to: `host:443` ``. Standard output and standard error are always granted.
- `# Structure`: one ``- `name`: one sentence.`` per function, `main` first.
3. For a program of more than one module, write one `ideas/<name>.md` per module and one
`ideas/ui/<name>.md` per screen, each with Purpose, Behaviours and Structure. Name each one
in the top idea's ``- Modules: `cart`, `ui/basket` ``. A module that uses another says
``- Uses: `cart` `` in its own `# Constraints`.
4. Write every sentence in STE. See [the STE rules](references/ste.md).
5. Do not write the frontmatter keys that lengua writes (`type`, `description`, `module`,
`source`, `uses`, `used_by`, `label`, `idea_sha256`, `source_sha256`). You may write OKF's
`title`, `tags` and `sources`; `check` keeps them.
6. Call `check` with the folder's absolute path. It returns every problem at once, each with
its file, line, code and message. Fix all of them, then call `check` again. Repeat until
`ok` is true.
7. Do not edit `index.md`, `log.md` or the frontmatter by hand; `check` writes them.
## A small idea
````
# Purpose
The program counts the words in a text. It reads the text from the standard input.
# Behaviours
## Count the words in a text
Given a text with two words on the standard input,
When the program runs,
Then it writes 2 and a line end to the standard output.
### Example: two words
- Standard input: "hello world\n"
- Expect standard output: "2\n"
- Expect exit code: 0
# Constraints
- Reads: standard input
- Memory: 16 MiB
- Time: 2 s
# Structure
- `main`: reads the standard input and writes the number of words.
````
Files in this package (3)
- SKILL.md 3 KB
- references/ste.md 2 KB
- references/test-format.md 2 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · laughing-hermit/lengua | 100 | Apache-2.0 |
| humansintheloop-dev/humansintheloop-dev-workflow-and-tools | 100 | Apache-2.0 |
Database snapshot: 13.11.2026 · package version d18d1ac608ea (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100simplified-technical-english
Write clear, unambiguous English for technical documentation using Simplified Technical English principles (adapted from ASD-STE100 Issue 9). Use this skill whenever you write or review PR descriptions, commit bodies, READMEs, API documentation, ADRs, changelogs, runbooks, error… - 100simplified-technical-english
Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, and when the user asks to write,… - 100simplified-technical-english
Writes and rewrites text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, and when the user asks to write,… - 100simplified-technical-english
Write and rewrite text in Simplified Technical English (ASD-STE100), a controlled language for clear technical documentation. Use when the user asks for STE, Simplified Technical English, controlled language, or plain technical writing, or asks to write, rewrite, review, or… - 100asd-ste100
Write, rewrite, or audit technical documentation in ASD-STE100 Simplified Technical English (Issue 9). Use when the user asks for Simplified Technical English or STE, mentions ASD-STE100, S1000D, ATA iSpec 2200, controlled or constrained English, or asks to make maintenance… - 100simplified
Explain any topic in Simplified Technical English (ASD-STE100 style) with a fixed skimmable structure. Use when the user types /simplified or asks for a simplified explanation.